Data processing systems and methods for automatically blocking the use of tracking tools

ABSTRACT

Data processing systems and methods, according to various embodiments, are adapted for determining a categorization for each tracking tool that executes on a particular webpage based on a variety of criteria, such as the purpose of the tracking tool and its source script. The system may compare the characteristics of tracking tools on a webpage to a database of known tracking tools to determine the appropriate categorization. When a user visits the webpage, the system analyzes these categories and determines whether the tracking tool should be permitted to run based on the categories and/or other criteria, such as whether the user has consented to the use of that type of tracking tool.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority from U.S. Provisional PatentApplication No. 62/946,908, filed Dec. 11, 2019, and is also acontinuation-in-part of U.S. patent application Ser. No. 16/872,130,filed May 11, 2020, which claims priority from U.S. Provisional PatentApplication No. 62/846,178, filed May 10, 2019 and U.S. ProvisionalPatent Application Ser. No. 62/846,184, filed May 10, 2019, and is alsoa continuation-in-part of U.S. patent application Ser. No. 16/778,709,filed Jan. 31, 2020, now U.S. Pat. No. 10,846,433, issued Nov. 24, 2020,which is a continuation-in-part of U.S. patent application Ser. No.16/560,963, filed Sep. 4, 2019, now U.S. Pat. No. 10,726,158, issuedJul. 28, 2020, which claims priority to U.S. Provisional PatentApplication Ser. No. 62/728,432, filed Sep. 7, 2018, and is also acontinuation-in-part of U.S. patent application Ser. No. 16/277,568,filed Feb. 15, 2019, now U.S. Pat. No. 10,440,062, issued Oct. 8, 2019,which claims priority from U.S. Provisional Patent Application Ser. No.62/631,684, filed Feb. 17, 2018 and U.S. Provisional Patent ApplicationSer. No. 62/631,703, filed Feb. 17, 2018, and is also acontinuation-in-part of U.S. patent application Ser. No. 16/159,634,filed Oct. 13, 2018, now U.S. Pat. No. 10,282,692, issued May 7, 2019,which claims priority from U.S. Provisional Patent Application Ser. No.62/572,096, filed Oct. 13, 2017 and U.S. Provisional Patent ApplicationSer. No. 62/728,435, filed Sep. 7, 2018, and is also acontinuation-in-part of U.S. patent application Ser. No. 16/055,083,filed Aug. 4, 2018, now U.S. Pat. No. 10,289,870, issued May 14, 2019,which claims priority from U.S. Provisional Patent Application Ser. No.62/547,530, filed Aug. 18, 2017, and is also a continuation-in-part ofU.S. patent application Ser. No. 15/996,208, filed Jun. 1, 2018, nowU.S. Pat. No. 10,181,051, issued Jan. 15, 2019, which claims priorityfrom U.S. Provisional Patent Application Ser. No. 62/537,839, filed Jul.27, 2017, and is also a continuation-in-part of U.S. patent applicationSer. No. 15/853,674, filed Dec. 22, 2017, now U.S. Pat. No. 10,019,597,issued Jul. 10, 2018, which claims priority from U.S. Provisional PatentApplication Ser. No. 62/541,613, filed Aug. 4, 2017, and is also acontinuation-in-part of U.S. patent application Ser. No. 15/619,455,filed Jun. 10, 2017, now U.S. Pat. No. 9,851,966, issued Dec. 26, 2017,which is a continuation-in-part of U.S. patent application Ser. No.15/254,901, filed Sep. 1, 2016, now U.S. Pat. No. 9,729,583, issued Aug.8, 2017, which claims priority from: (1) U.S. Provisional PatentApplication Ser. No. 62/360,123, filed Jul. 8, 2016; (2) U.S.Provisional Patent Application Ser. No. 62/353,802, filed Jun. 23, 2016;(3) U.S. Provisional Patent Application Ser. No. 62/348,695, filed Jun.10, 2016. The disclosures of all of the above patent applications arehereby incorporated herein by reference in their entirety.

BACKGROUND

Over the past years, privacy and security policies, and relatedoperations have become increasingly important. Breaches in security,leading to the unauthorized access of personal data (which may includesensitive personal data) have become more frequent among companies andother organizations of all sizes. Such personal data may include, but isnot limited to, personally identifiable information (PII), which may beinformation that directly (or indirectly) identifies an individual orentity. Examples of PII include names, addresses, dates of birth, socialsecurity numbers, and biometric identifiers such as a person'sfingerprints or picture. Other personal data may include, for example,customers' Internet browsing habits, purchase history, or even theirpreferences (e.g., likes and dislikes, as provided or obtained throughsocial media).

Many organizations that obtain, use, and transfer personal data,including sensitive personal data, have begun to address these privacyand security issues. To manage personal data, many companies haveattempted to implement operational policies and processes that complywith legal and industry requirements. However, there is an increasingneed for improved systems and methods to manage personal data in amanner that complies with such policies.

Similarly, as individuals have become more aware of the risks associatedwith the theft or misuse of their personal data, they have soughtadditional tools to help them manage which entities process theirpersonal data. There is currently a need for improved tools that wouldallow individuals to minimize the number of entities that process theirpersonal data—especially entities that the individual doesn't activelydo business with.

Among the other information that an organization may collect about auser, various websites use third-party cookies to track a user and/orthe user's behavior as they are using a browser to visit differentwebsites. Such cookies may, for example, track a user's interests,location, age, and/or search trends. This information may then be soldto marketers that may use the information, for example, to provide theuser with advertisements that are customized to the user.

Many privacy laws and regulations require that websites obtain consentfrom a user before using cookies to collecting the user's personal data.Many users consent to the use of such cookies because the use of cookiesmay enhance the user's experience on websites. For example, some usersmay consent to the use of cookies as they browse on-line shoppingwebsites because they want to receive offers (e.g., discounts) that aretailored to their needs and interests. However, with theirprivacy-related interests in mind, other users prefer to block the useof some or all cookies.

There is currently a need for improved tools for automatically blockingtracking technologies associated with a website, such as trackingtechnologies that process personal data in one or more categories forwhich the relevant user has not provided consent.

SUMMARY

A computer-implemented data processing method for managing a consentreceipt under a transaction, according to particular embodiments,comprises: (1) providing a user interface for initiating a transactionbetween an entity and a data subject; (2) receiving a request toinitiate a transaction between the entity and the data subject; (3) inresponse to the request, generating, by a third party consent receiptmanagement system, a unique consent receipt key; (4) receiving, from thedata subject, a unique subject identifier; (5) electronically storingthe unique subject identifier, the unique consent receipt key, and aunique transaction identifier associated with the transaction incomputer memory; (6) electronically associating the unique subjectidentifier, the unique consent receipt key, and the unique transactionidentifier; and (7) in response to receiving the request, transmitting aconsent receipt to the data subject, the consent receipt comprising atleast the unique subject identifier and the unique consent receipt key.

A computer-implemented data processing method for managing a consentreceipt under a transaction, according to various embodiments,comprises: (1) providing a user interface for initiating a transactionbetween an entity and a data subject; (2) receiving, from a computingdevice associated with the data subject via the user interface, arequest to initiate a transaction between the entity and the datasubject; (3) in response to receiving the request: (A) generating, by aconsent receipt management system, a unique consent receipt key; and (B)initiating a virtual browsing session on a consent receipt captureserver; (4) accessing a webpage hosting the user interface using avirtual browser during the virtual browsing session; (5) scanning thewebpage to identify the user interface; (6) capturing the user interfacein an unfilled state; (7) electronically storing a unique subjectidentifier associated with the data subject, the unique consent receiptkey, a unique transaction identifier associated with the transaction,and the capture of the user interface in computer memory; (8)electronically associating the unique subject identifier, the uniqueconsent receipt key, the unique transaction identifier, and the captureof the user interface; and (9) in response to receiving the request,optionally transmitting a consent receipt to the data subject, theconsent receipt comprising at least the unique subject identifier andthe unique consent receipt key.

A consent receipt management system, according to any embodimentdescribed herein, may comprise: (1) one or more processors; and (2)computer memory. In any embodiment described herein, the consent receiptmanagement system may be configured for: (1) receiving a request toinitiate a transaction between an entity and a data subject, thetransaction involving collection or processing of personal dataassociated with the data subject by the entity as part of a processingactivity undertaken by the entity that the data subject is consenting toas part of the transaction; (2) in response to receiving the request:(A) identifying a transaction identifier associated with thetransaction; (B) generating, a unique consent receipt key for thetransaction; and (C) determining a unique subject identifier for thedata subject; (3) electronically storing the unique subject identifier,the unique consent receipt key, and the transaction identifier incomputer memory; (4) electronically associating the unique subjectidentifier, the unique consent receipt key, and the transactionidentifier; (5) generating a consent record for the transaction, theconsent receipt comprising at least the unique subject identifier andthe unique consent receipt key; and (6) electronically transmitting theconsent record to the data subject.

A computer-implemented data processing method for managing a consentreceipt under a transaction, in any embodiment described herein, maycomprise: (1) providing a user interface for initiating a transactionbetween an entity and a data subject; (2) receiving a request toinitiate a transaction between the entity and the data subject; (3) inresponse to the request, generating, by a third party consent receiptmanagement system, a unique consent receipt key; (4) receiving, from thedata subject, a unique subject identifier; (5) electronically storingthe unique subject identifier, the unique consent receipt key, and aunique transaction identifier associated with the transaction incomputer memory; (6) electronically associating the unique subjectidentifier, the unique consent receipt key, and the unique transactionidentifier; and (7) in response to receiving the request, transmitting aconsent receipt to the data subject, the consent receipt comprising atleast the unique subject identifier and the unique consent receipt key.

A computer-implemented data processing method for identifying one ormore pieces of personal data associated with a data subject within adata system in order to fulfill a data subject access request, in anyembodiment described herein, comprises: (1) receiving, by one or moreprocessors, from a data subject, a data subject access request; (2)processing the data subject access request by identifying the one ormore pieces of personal data associated with the data subject; and (3)in response to identifying the one or more pieces of personal data,taking one or more actions such as, for example: (1) deleting the one ormore pieces of personal data from the data system; (2) modifying atleast one of the one or more pieces of personal data and storing themodified at least one of the one or more pieces of personal data in thedata system; and (3) generating a report comprising the one or morepieces of personal data and providing the report to the data subject. Invarious embodiments, identifying the one or more pieces of personal dataassociated with the data subject comprises scanning one or more datainventories stored within the data system for the one or more pieces ofpersonal data;

A data processing data inventory generation system, according to variousembodiments, comprises: (1) one or more processors; (2) computer memory;and (3) a computer-readable medium storing computer-executableinstructions. In various embodiments, the computer-executableinstructions, when executed by the one or more processors, cause the oneor more processors to perform operations comprising: (1) identifying aprimary data asset that collects or stores personal data of one or moredata subjects; and (2) generating a data inventory for the primary dataasset, the data inventory storing one or more primary data assetinventory attributes. In particular embodiments, the one or more primarydata asset inventory attributes comprise: (1) a type of personal datacollected or stored by the primary data asset; and (2) primary transferdata associated with the personal data and the primary data asset. Inparticular embodiments, the computer-executable instructions, whenexecuted by the one or more processors, further cause the one or moreprocessors to perform operations comprising: (1) identifying a transferdata asset based at least in part on the primary transfer data; (2)modifying the data inventory to include the transfer data asset, thetransfer data asset storing one or more transfer data asset inventoryattributes comprising the primary transfer data; (3) digitally storingthe data inventory in the computer memory; and (4) electronicallylinking the primary data asset to the transfer data asset in the datainventory.

A computer-implemented data processing method of generating a datainventory for a plurality of inter-related data assets utilized in theprocessing of one or more pieces of personal data, according to variousembodiments, comprises: (1) identifying, by one or more processors, fromthe plurality of inter-related data assets, a storage asset, the storageasset storing the one or more pieces of personal data collected from oneor more data subjects; (2) identifying, by one or more processors, fromthe plurality of inter-related data assets, a collection asset thattransfers the one or more pieces of personal data to the storage asset;(3) identifying, by one or more processors, from the plurality ofinter-related data assets, a transfer asset to which the storage assettransfers the one or more pieces personal data; (4) digitally storing,by one or more processors, in computer memory, one or more storage assetinventory attributes comprising a type of personal data stored by thestorage asset; (5) digitally storing, by one or more processors, incomputer memory, one or more collection asset inventory attributescomprising the one or more pieces of personal data that the collectionasset transfers to the storage asset; (6) digitally storing, by one ormore processors, in computer memory, one or more transfer assetinventory attributes comprising the one or more pieces of personal datathat the storage asset transfers to the transfer asset; and (7)generating the data inventory.

In particular embodiments, generating the data inventory comprises: (1)associating the storage asset with the one or more storage assetinventory attributes in computer memory; (2) associating the collectionasset with the one or more collection asset inventory attributes incomputer memory; (3) associating the transfer asset with the one or moretransfer asset inventory attributes in computer memory; (4)electronically linking the collection asset to the storage asset incomputer memory; (5) electronically linking the storage asset to thetransfer asset; and (6) electronically mapping the one or more pieces ofpersonal data to the collection asset, the storage asset, and thetransfer asset.

A computer-implemented data processing method for generating a datamodel of personal data processing activities, according to particularembodiments, comprises: (1) generating a data model for one or more dataassets used in the collection or storage of personal data; (2) digitallystoring the data model in computer memory; (3) identifying a first dataasset of the one or more data assets; (4) modifying the data model toinclude the first data asset; (5) generating a data inventory for thefirst data asset in the data model; (6) associating the data inventorywith the first data asset in computer memory; and (7) mapping the firstdata asset to at least one of the one or more data assets in the datamodel. In various embodiments, the data inventory comprises one or moreinventory attributes such as, for example: (1) one or more processingactivities associated with the first data asset; (2) transfer dataassociated with the first data asset; and (3) one or more pieces ofpersonal data associated with the first asset.

A computer-implemented data processing method for optimizing provisionof consent to the use of one or more cookies at a particular web domainby one or more users accessing the particular web domain, according tovarious embodiments, comprise: (1) receiving, by one or more processors,a request to initiate a cookie consent interface consent conversion testfor the particular web domain, the request comprising: (a) the domainname; (b) a first selection of a first consent interface templatevariant; (c) a second selection of a second consent interface templatevariant; and (d) at least one success criteria; (2) in response toreceiving the request, initiating, by one or more processors, the cookieconsent interface consent conversion test for the particular web domainby: (a) presenting, to a first portion of the one or more usersaccessing the particular web domain, the first consent interfacetemplate variant; (b) presenting, to a second portion of the one or moreusers accessing the particular web domain, the second consent interfacetemplate variant; (3) receiving, by one or more processors, for eachrespective user of the first portion of the one or more users accessingthe particular web domain, first consent data via the first consentinterface template variant; (4) receiving, by one or more processors,for each respective user of the second portion of the one or more usersaccessing the particular web domain, second consent data via the secondconsent interface template variant; (5) analyzing, by one or moreprocessors, the first consent data and the second consent data todetermine a more successful consent interface template of the firstconsent interface template variant and the second consent interfacetemplate variant based at least in part on the at least one successcriteria; and (6) in response to determining the more successful consentinterface template of the first consent interface template variant andthe second consent interface template: (a) completing the cookie consentinterface consent conversion test; and (b) presenting, by one or moreprocessors, the more successful consent interface template to anysubsequent user that accesses the particular web domain after completingthe cookie consent interface consent conversion test for at least aparticular length of time.

A computer system, in particular embodiments, comprises at least oneprocessor and memory. In various embodiments, the computer system isconfigured for: (1) receiving, from a plurality of users via arespective computing device, a plurality of requests to access aparticular domain; (2) in response to receiving the plurality ofrequests, causing, for each of the plurality of requests, eachrespective computing device to display, on at least one webpageassociated with the particular domain, a particular cookie consentinterface from a group of at least two test interfaces, wherein the atleast two test interfaces comprise: (a) a first cookie consent testinterface having at least one first test attribute; and (b) a secondcookie consent test interface having at least one second test attribute;(3) receiving, via the particular cookie consent interface, consent datafor each of the plurality of requests, the consent data indicating alevel of consent provided by each of the plurality of users for the useof one or more cookies by the particular domain; (4) analyzing theconsent data to identify which of the first cookie consent testinterface and the second cookie consent interface most closely matchesone or more consent criteria; (5) determining that the particular cookieconsent test interface most closely matches the one or more consentcriteria; and (6) in response to determining the particular cookieconsent test interface most closely matches the one or more consentcriteria, at least temporarily implementing the particular cookieconsent test interface as a primary cookie consent interface for use bythe particular domain.

A computer-implemented data processing method for automaticallyselecting a user interface for the collection of consent to processdata, according to various embodiments, comprises: (a) receiving, from afirst user via a first computing device, a request to access a website;(b) in response to receiving the request, determining whether the firstuser has previously consented to the use of one or more cookies by thewebsite; (c) in response to determining that the user has not previouslyconsented to the use of one or more cookies by the website, causing thefirst computing device to display a first cookie consent interface froma group of at least two test consent interfaces; (d) collecting consentdata for the first user based on one or more selections made by thefirst user via the first cookie consent interface; (e) repeating stepsa-d for a plurality of other users of the website, such that each of theat least two consent interfaces are displayed to at least a portion ofthe plurality of other users; (f) analyzing the consent data to identifya particular interface of the at least two consent interfaces thatresults in a more desired level of consent; and (g) in response toidentifying the particular interface, implementing the particularinterface as the primary consent interface for use by the website.

A computer-implemented data processing method for managing a consentreceipt under a transaction, in particular embodiments, comprises: (1)providing a user interface for initiating a transaction between anentity and a data subject; (2) receiving, from a computing deviceassociated with the data subject via the user interface, a request toinitiate a transaction between the entity and the data subject; (3) inresponse to receiving the request: (a) generating, by a consent receiptmanagement system, a unique consent receipt key; and (b) initiating avirtual browsing session on a consent receipt capture server; (4)accessing a webpage hosting the user interface using a virtual browserduring the virtual browsing session; (5) scanning the webpage toidentify the user interface; (6) capturing the user interface in anunfilled state; (7) electronically storing a unique subject identifierassociated with the data subject, the unique consent receipt key, aunique transaction identifier associated with the transaction, and thecapture of the user interface in computer memory; (8) electronicallyassociating the unique subject identifier, the unique consent receiptkey, the unique transaction identifier, and the capture of the userinterface; and (9) in response to receiving the request, optionallytransmitting a consent receipt to the data subject, the consent receiptcomprising at least the unique subject identifier and the unique consentreceipt key.

A computer-implemented data processing method for managing a consentreceipt under a transaction, in various embodiments, comprises: (1)providing a user interface for initiating a transaction between anentity and a data subject; (2) receiving a request from a data subjectto initiate a transaction between the entity and the data subject; (3)in response to the request: (a) prompting the data subject to provideconsent to the entity for processing personal data associated with thedata subject as part of the transaction; and (b) generating a uniqueconsent receipt key; (4) receiving, from the data subject, a uniquesubject identifier; (5) electronically storing the unique subjectidentifier, the unique consent receipt key, a unique transactionidentifier associated with the transaction, and an indication of theconsent in a consent record in computer memory; and (6) electronicallyassociating the unique subject identifier, the unique consent receiptkey, the unique transaction identifier, and the indication of theconsent.

A computer-implemented data processing method for managing andmaintaining a consent receipt under a transaction, in any embodimentdescribed herein, may comprise: (1) providing a user interface forinitiating a transaction between an entity and a data subject; (2)receiving a request to initiate the transaction between the entity andthe data subject via the user interface; (3) in response to the request,generating, a unique consent receipt key; (4) electronically storing aunique subject identifier, the unique consent receipt key, and a uniquetransaction identifier associated with the transaction in computermemory; (5) electronically associating the unique subject identifier,the unique consent receipt key, and the unique transaction identifier;(6) determining whether the consent receipt is subject to expiration;and (7) in response to determining that consent receipt is subject toexpiration, automatically taking an action under the transaction toavoid the expiration.

A computer-implemented data processing method for automating processingof data of one or more data subjects, in particular embodiments,comprises: (1) providing, by one or more processors, to the one or moredata subjects, a user interface for initiating a transaction between theentity and each respective data subject of the one or more datasubjects; (2) receiving, by one or more processors, a plurality ofrequests to initiate a plurality of transactions, each of the pluralityof transactions comprising a respective transaction between the entityand a respective data subject of the one or more data subjects; (3) inresponse to receiving each of the plurality of requests, generating, byone or more processors, a unique respective consent receipt key, theunique respective consent receipt key comprising an indication ofconsent by each of the one or more data subjects to the processing ofthe one or more pieces of personal data; (4) electronically storing andassociating, by one or more processors, each unique respective consentreceipt key, a unique identifier for the respective data subject, and aunique transaction identifier associated with the respective transactionof the plurality of transactions in computer memory; (5) receiving anindication that a data system associated with the entity has processed anew piece of personal data associated with a particular data subject ofthe one or more data subjects as part of a particular transaction of theplurality of transactions; (6) in response to receiving the indicationthat the data system has processed the new piece of personal data,determining, based on the plurality of consent receipts, whether theparticular data subject has provided the indication of consent for theprocessing of the new piece of personal data as part of the particulartransaction; (7) in response to determining that the particular datasubject has provided the indication of the consent, automaticallyprocessing the new piece of personal data; and (8) in response todetermining that the particular data subject has not provided theindication of the consent, automatically taking an action selected fromthe group consisting of: (a) automatically ceasing processing of the newpiece of personal data; (b) identifying a legal basis for processing thenew piece of personal data absent the indication of the consent, and, inresponse to identifying the legal basis, automatically processing thenew piece of personal data; and (c) prompting the particular datasubject to provide the indication of the consent.

A computer-implemented data processing method for blocking one or moreprocesses based on consent data, in any embodiment described herein, maycomprise: (1) receiving an indication that one or more entity systemsare processing one or more pieces of personal data associated with aparticular data subject; (2) in response to receiving the indication,identifying at least one process for which the one or more pieces ofpersonal data are being processed; (3) determining, using a consentreceipt management system, whether the data subject has provided validconsent for the processing of the one or more pieces of personal datafor the at least one process; and (4) at least partially in response todetermining that the data subject has not provided valid consent for theprocessing of the one or more pieces of personal data for the at leastone process, automatically blocking the processing.

A consent receipt management and automated process blocking system,according to particular embodiments, comprises one or more processors,and computer memory that stores one or more consent records associatedwith a unique subject identifier, each of the one or more consentrecords being associated with a respective transaction of a plurality oftransactions involving a data subject and an entity. In variousembodiments, the consent receipt management and automated processblocking system is configured for: (1) receiving an indication that oneor more computer systems are attempting to process one or more pieces ofpersonal data associated with a data subject; (2) determining a purposeof processing the one or more pieces of personal data; (3) accessing theone or more consent records; (4) determining, based at least in part onthe purpose of the processing and the one or more consent records,whether the data subject has provided valid consent to the processing ofthe one or more pieces of personal data for the purpose; (5) in responseto determining that the data subject has provided the valid consent,automatically processing the one or more pieces of personal data for thepurpose; and (5) in response to determining that the data subject hasnot provided the valid consent, at least temporarily blocking theprocessing of the one or more pieces of personal data.

A computer-implemented data processing method for monitoring consentrecord rate change of a particular capture point, in variousembodiments, comprises: (1) providing a user interface at a particularcapture point for initiating a transaction between an entity and a datasubject; (2) receiving, from a respective computing device associatedwith each of a plurality of data subjects via the user interface, aplurality of requests to initiate a respective transaction between theentity and each of the plurality of data subjects; (3) in response toreceiving each of the plurality of requests: (a) generating, by aconsent receipt management system, a unique consent receipt key for eachrespective request of the plurality of requests; (b) storing, for eachrespective request, a respective consent record comprising the uniqueconsent receipt key; (4) monitoring the particular capture point todetermine a rate of consent records generated at the particular capturepoint; (5) identifying a change in the rate of consent records generatedat the particular capture point; and (6) in response to identifying thechange in the rate of consent records generated at the particularcapture point, generating an electronic alert and transmitting theelectronic alert to an individual responsible for the particular capturepoint.

A consent receipt management system, according to various embodiments,comprises one or more processors and computer memory that stores aplurality of consent records associated with a unique subjectidentifier, each of the plurality of consent records being associatedwith a respective transaction of a plurality of transactions involving adata subject and an entity. In particular embodiments, the consentreceipt management system is configured for: (1) receiving, at aparticular consent capture point, a request to initiate a transactionbetween the entity and the data subject, the transaction involvingcollection or processing of personal data associated with the datasubject by the entity as part of a processing activity undertaken by theentity that the data subject is consenting to as part of thetransaction; (2) in response to receiving the request: (a) identifying atransaction identifier associated with the transaction; (b) identifyinga capture point identifier for the particular consent capture point; (c)generating, a unique consent receipt key for the transaction; and (d)determining a unique subject identifier for the data subject; (3)electronically storing the unique subject identifier, the unique consentreceipt key, the capture point identifier, and the transactionidentifier in computer memory; (4) electronically associating the uniquesubject identifier, the unique consent receipt key, the capture pointidentifier, and the transaction identifier; (5) generating a consentrecord for the transaction, the consent record comprising at least theunique subject identifier and the unique consent receipt key; (6)monitoring the particular consent capture point to determine a consentrecord rate for the particular consent capture point; (7) analyzing theconsent record rate to identify a particular change in the consentrecord rate; and (8) in response to identifying the particular change inthe consent record rate, taking one or more automated actions.

A computer-implemented data processing method for managing a consentcapture point, in various embodiments, comprises: (1) providing, at theconsent capture point, a user interface for initiating a transactionbetween an entity and a data subject; (2) receiving a request toinitiate the transaction between the entity and the data subject; (3) inresponse to receiving the request, generating, by a third-party consentreceipt management system, a unique consent receipt key; (4) receiving,from the data subject, a unique subject identifier; (5) identifying acapture point identifier associated with the capture point; (6)electronically storing the unique subject identifier, the unique consentreceipt key, the capture point identifier, and a unique transactionidentifier associated with the transaction in a consent record; (7)electronically associating the unique subject identifier, the uniqueconsent receipt key, the consent capture point identifier, and theunique transaction identifier; (8) accessing a plurality of consentrecords associated with the capture point identifier; (9) analyzing eachof the plurality of consent records associated with the consent capturepoint identifier to determine a consent record rate for the consentcapture point; (10) monitoring the consent record rate for the consentcapture point to identify a particular change to the consent recordrate; and (11) in response to identifying the particular change in theconsent record rate, taking one or more automated actions.

A computer-implemented data processing method for managing a consentreceipt under a transaction, in various embodiments, comprises: (1)receiving a request to initiate a transaction between an entity and adata subject; (2) determining that the transaction includes one or moretypes of personal data of the data subject involved in the transaction;(3) determining that the data subject is required to consent to the oneor more types of personal data involved in the transaction; (4)determining, based at least in part on the one or more types of personaldata involved in the transaction, an age required for the data subjectto provide valid consent; (5) prompting the data subject to provide aresponse to each of one or more questions; (6) receiving the response toeach of the one or more questions from the data subject; (7) calculatinga predicted age of the data subject based at least in part on theresponse to each of the one or more questions; (8) comparing thepredicted age of the data subject to the age required for the datasubject to provide valid consent; (9) in response to determining thatthe predicted age of the data subject is at least equal to the agerequired for the data subject to provide valid consent, generating aunique consent receipt key for the data subject; and (10) in response todetermining that the predicted age of the data subject is less than theage required for the data subject to provide valid consent, terminatingthe transaction.

A computer-implemented data processing method for managing a consentreceipt under a transaction in particular embodiments, comprises: (1)receiving a data subject access request from a requestor that is arequest for a particular organization to perform one or more actionswith regard to one or more pieces of personal data associated with anidentified data subject that the particular organization has obtained onthe identified data subject, wherein the data subject access requestcomprises one or more request parameters; (2) in response to receivingthe data subject access request from the requestor, validating anidentity of the requestor by prompting the requestor to identifyinformation associated with the identified data subject, whereinvalidating the identity of the requestor comprises: (a) accessing, viaone or more computer networks, one or more third-party data aggregationsystems; (b) confirming, based at least in part on information receivedvia the one or more third-party data aggregation systems, that theidentified data subject exists; and (c) in response to determining thatthe identified data subject exists, confirming, based at least in parton the information received via the one or more third-party dataaggregation systems and the one or more request parameters, that therequestor is the identified data subject; (3) in response to validatingthe identity of the requestor, processing the request by identifying oneor more pieces of personal data associated with the identified datasubject, the one or more pieces of personal data being stored in one ormore data repositories associated with the particular organization; and(4) taking the one or more actions based at least in part on the datasubject access request, the one or more actions including one or moreactions related to the one or more pieces of personal data associatedwith the identified data subject.

A computer-implemented data processing method for managing a consentreceipt under a transaction, according to particular embodiments,comprises: (1) receiving a request to initiate a transaction between anentity and a data subject; (2) determining that the transaction includesone or more types of personal data of the data subject involved in thetransaction; (3) determining that the data subject is required toconsent to the one or more types of personal data involved in thetransaction; (4) determining, based at least in part on the one or moretypes of personal data involved in the transaction, an age required forthe data subject to provide valid consent; (5) determining that an ageof the data subject is less than the age required for the data subjectto provide valid consent; (6) in response to determining that the age ofthe data subject is less than the age required for the data subject toprovide valid consent, communicating with an identified guardian of thedata subject to receiving valid consent to fulfill the transaction.

Various other embodiments of the system are described in the listing ofconcepts below:

1. A computer-implemented data processing method for managing a consentreceipt under a transaction, according to various embodiments comprises:

providing, by one or more computer processors, at the consent capturepoint, a user interface for initiating a transaction between an entityand a data subject, the transaction involving processing personal dataof the data subject by the entity;

receiving, by one or more computer processors, a request to initiate thetransaction between the entity and the data subject;

in response to receiving the request, generating, by one or morecomputer processors, by a consent receipt management system, a uniqueconsent receipt key;

receiving, by one or more computer processors, from the data subject, aunique subject identifier;

requesting, by one or more computer processors, from the data subject,at least one piece of identifying information;

receiving, by one or more computer processors, the at least one piece ofidentifying information from the data subject;

determining, by one or more computer processors, based at least in parton the at least one piece of identifying information, an age of the datasubject;

identifying, by one or more computer processors, a capture pointidentifier associated with the capture point;

electronically storing, by one or more computer processors, the uniquesubject identifier, the unique consent receipt key, the capture pointidentifier, the age of the data subject, and a unique transactionidentifier associated with the transaction in a consent record;

electronically associating, by one or more computer processors, theunique subject identifier, the unique consent receipt key, the consentcapture point identifier, the age of the data subject, and the uniquetransaction identifier in computer memory;

determining, by one or more computer processors, based on the age of thedata subject and the transaction, whether the data subject meets one ormore age criteria for the processing of personal data under thetransaction;

in response to determining the data subject meets the one or more agecriteria for the processing of personal data under the transaction,modifying, by one or more computer processors, the consent record toelectronically store an indication that the data subject has providedvalid consent for the transaction;

in response to determining the data subject does not meet the one ormore age criteria for the processing of personal data under thetransaction, modifying, by one or more computer processors, the consentrecord to include an indication that the data subject has providedinvalid consent.

2. The computer-implemented data processing method of Concept 1, in anyembodiment described herein, may comprise:

receiving a request from a data system associated with the entity toprocess a new piece of personal data associated with the data subject aspart of the transaction;

in response to receiving the request to process the new piece ofpersonal data, determining whether the consent record comprises theindication of valid consent or the indication of invalid consent;

in response to determining that the consent record comprises theindication of valid consent, automatically processing the new piece ofpersonal data; and

in response to determining that the consent record comprises theindication of invalid consent, automatically ceasing processing of thenew piece of personal data

3. The computer-implemented data processing method of Concept 2, whereindetermining, based at least in part on the at least one piece ofidentifying information, the age of the data subject may comprise:

accessing, via one or more computer networks, one or more third-partydata aggregation systems; and

determining, based at least in part on the at least one piece ofidentifying information using the one or more third-party dataaggregation systems, the age of the data subject.

4. The computer-implemented data processing method of Concept 2,wherein:

the at least one piece of identifying information comprises the age ofthe data subject; and

the method, in any embodiment described herein, may comprise:

-   -   prompting the data subject to provide a response to each of one        or more questions;    -   receiving the response to each of the one or more questions from        the data subject;    -   confirming the age of the data subject based at least in part on        the response to each of the one or more questions.        5. The computer-implemented data processing method of Concept 4,        wherein the one or more questions are related to a logic problem        that include, for example: (i) mathematics, (ii) reading        comprehension.        6. The computer-implemented data processing method of Concept 2,        wherein determining the age of the data subject may comprise:

accessing, via one or more computer networks, the one or morethird-party data aggregation systems; and

determining, based at least in part on the at least one piece ofidentifying information using the one or more third-party dataaggregation systems, identifying information about the data subject;

generating, based at least in part on the identifying information aboutthe data subject, at least one threshold identity confirmation question;

prompting the data subject to provide a response to the at least onethreshold identity confirmation question; and

comparing the response to the identifying information about the datasubject to determine the age of the data subject.

7. The computer-implemented data processing method of Concept 6, whereinthe identifying information about the data subject may comprise a yearof birth of the data subject.8. The computer-implemented data processing method of Concept 1, in anyembodiment described herein, may comprise:

in response to determining the data subject does not meet the one ormore age criteria for the processing of personal data under thetransaction:

-   -   prompting the data subject to provide one or more contact        details for a guardian of the data subject;    -   accessing an electronic guardian registry for one or more data        subjects;    -   determining, based at least in part on the one or more contact        details for the guardian of the data subject using the        electronic guardian registry, that the data subject has an        identified registered guardian; and    -   communicating with the identified guardian, via the one or more        contact details, to receive the valid consent to fulfill the        transaction on behalf of the data subject by:        -   transmitting an electronic message to the identified            guardian; and        -   prompting the identified guardian to provide the valid            consent via the electronic message.            9. The computer-implemented data processing method of            Concept 8, in any embodiment described herein, may comprise:    -   receiving the valid consent from the identified guardian; and    -   in response to receiving the valid consent from the identified        guardian, modifying the consent record to electronically store        an indication that the identified guardian has provided valid        consent for the transaction        10. A computer-implemented data processing method for managing a        consent receipt under a transaction, in particular embodiments,        comprises:

receiving, by one or more computer processors, a request to initiate atransaction between an entity and a data subject;

determining, by one or more computer processors, that the transactionincludes one or more types of personal data of the data subject involvedin the transaction;

determining, by one or more computer processors, that the data subjectis required to consent to the one or more types of personal datainvolved in the transaction;

determining, based at least in part on the one or more types of personaldata involved in the transaction, an age required for the data subjectto provide valid consent;

prompting, by one or more computer processors, the data subject toprovide a response to each of one or more questions;

receiving the response, by one or more computer processors, to each ofthe one or more questions from the data subject;

calculating, by one or more computer processors, a predicted age of thedata subject based at least in part on the response to each of the oneor more questions;

comparing, by one or more computer processors, the predicted age of thedata subject to the age required for the data subject to provide validconsent;

in response to determining that the predicted age of the data subject isat least equal to the age required for the data subject to provide validconsent, generating, by one or more computer processors, a uniqueconsent receipt key for the data subject; and

in response to determining that the predicted age of the data subject isless than the age required for the data subject to provide validconsent, terminating, by one or more computer processors, thetransaction.

11. The computer-implemented data processing method of Concept 10,wherein the one or more questions are related to a logic problem thatinclude at least one subject such as: (i) mathematics, (ii) readingcomprehension.12. The computer-implemented data processing method of Concept 10, inany embodiment described herein, may comprise:

accessing, via one or more computer networks, one or more third-partydata aggregation systems; and

confirming, based at least in part on information received via the oneor more third-party data aggregation systems, the predicted age of thedata subject.

13. The computer-implemented data processing method of Concept 12,wherein confirming the predicted age of the data subject may comprise:

generating, based at least in part on the information received via theone or more third-party data aggregation systems, at least one thresholdidentity confirmation question;

prompting the data subject to provide a response to the at least onethreshold identity confirmation question; and

comparing the response to the information received via the one or morethird-party data aggregation systems to validate the identity of therequestor.

14. The computer-implemented data processing method of Concept 13,wherein the information received via the one or more third-party dataaggregation systems may comprise a year of birth of the data subject.15. The computer-implemented data processing method of Concept 12, inany embodiment described herein, may comprise:

prompting the data subject to provide one or more additional pieces ofinformation in order to determine an actual age of the data subject;

receiving the one or more additional pieces of information; and

comparing the one or more additional pieces of information received fromthe data subject to corresponding information accessed via the one ormore third-party data aggregation systems in order to validate theidentity of the requestor.

16. The computer-implemented data processing method of Concept 15,wherein the one or more additional pieces of information may compriseone or more images provided by the data subject via a computing deviceassociated with the data subject.17. A consent receipt management system, in various embodiments,comprises:

one or more processors; and

computer memory that stores a plurality of consent records associatedwith a unique subject identifier, each of the plurality of consentrecords being associated with a respective transaction of a plurality oftransactions involving a data subject and an entity, wherein the consentreceipt management system, in various embodiments, is configured for:

-   -   receiving, at a particular consent capture point, a request to        initiate a transaction between the entity and the data subject,        the transaction involving collection or processing of personal        data associated with the data subject by the entity as part of a        processing activity undertaken by the entity that the data        subject is consenting to as part of the transaction;    -   in response to receiving the request:        -   identifying a transaction identifier associated with the            transaction;        -   identifying a capture point identifier for the particular            consent capture point;        -   generating, a unique consent receipt key for the            transaction; and        -   determining a unique subject identifier for the data            subject;        -   requesting, from the data subject, at least one piece of            identifying information;        -   receiving the at least one piece of identifying information            from the data subject;        -   determining, based at least in part on the at least one            piece of identifying information, an age of the data            subject;        -   electronically storing the unique subject identifier, the            unique consent receipt key, the capture point identifier,            the age of the data subject, and the transaction identifier            in computer memory;        -   electronically associating the unique subject identifier,            the unique consent receipt key, the capture point            identifier, the age of the data subject, and the transaction            identifier;        -   generating a consent record for the transaction, the consent            record comprising at least the unique subject identifier,            the age of the data subject, and the unique consent receipt            key;

receiving an indication that a data system associated with the entityhas processed a new piece of personal data associated with the datasubject as part of the transaction;

in response to receiving the indication that the data system associatedwith the entity has processed the new piece of personal data,determining, based on the age of the data subject and the transaction,whether the data subject meets one or more age criteria for theprocessing of data under the transaction;

in response to determining that the data subject meets the one or moreage criteria, automatically processing the new piece of personal data;and

in response to determining that the data subject does not meet the oneor more age criteria, automatically taking an action selected from thegroup consisting of:

-   -   automatically ceasing processing of the new piece of personal        data; and    -   prompting the data subject to provide one or more contact        details for a guardian of the data subject.        18. The consent receipt management system of Concept 17, wherein        determining, based at least in part on the at least one piece of        identifying information, the age of the data subject may        comprise:

accessing, via one or more computer networks, one or more third-partydata aggregation systems; and

determining, based at least in part on the at least one piece ofidentifying information using the one or more third-party dataaggregation systems, the age of the data subject.

19. The consent receipt management system of Concept 17, wherein:

the at least one piece of identifying information comprises the age ofthe data subject; and

the consent receipt management system is configured for:

-   -   prompting the data subject to provide a response to each of one        or more questions;    -   receiving the response to each of the one or more questions from        the data subject;    -   confirming the age of the data subject based at least in part on        the response to each of the one or more questions.        20. The consent receipt management system of Concept 17, wherein        the consent receipt management system may be configured for:

accessing an electronic guardian registry for one or more data subjects;

determining, based at least in part on the one or more contact detailsfor the guardian of the data subject using the electronic guardianregistry, that the data subject has an identified registered guardian;and

communicating with the identified guardian, via the one or more contactdetails, to receive valid consent to fulfill the transaction on behalfof the data subject by:

-   -   transmitting an electronic message to the identified guardian;        and    -   prompting the identified guardian to provide the valid consent        via the electronic message.

Various other embodiments of the system, such as any embodimentdescribed herein, may further include one or more features described inthe listing of concepts below:

1. A computer-implemented data processing method for managing a consentreceipt under a transaction, in particular embodiments, comprises:

providing, by one or more computer processors, at the consent capturepoint, a user interface for initiating a transaction between an entityand a data subject, the transaction involving processing personal dataof the data subject by the entity;

receiving, by one or more computer processors, a request to initiate thetransaction between the entity and the data subject;

in response to receiving the request, generating, by one or morecomputer processors, by a consent receipt management system, a uniqueconsent receipt key;

receiving, by one or more computer processors, from the data subject, aunique subject identifier;

requesting, by one or more computer processors, from the data subject,at least one piece of identifying information;

receiving, by one or more computer processors, the at least one piece ofidentifying information from the data subject;

determining, by one or more computer processors, based at least in parton the at least one piece of identifying information, an age of the datasubject;

identifying, by one or more computer processors, a capture pointidentifier associated with the capture point;

electronically storing, by one or more computer processors, the uniquesubject identifier, the unique consent receipt key, the capture pointidentifier, the age of the data subject, and a unique transactionidentifier associated with the transaction in a consent record;

electronically associating, by one or more computer processors, theunique subject identifier, the unique consent receipt key, the consentcapture point identifier, the age of the data subject, and the uniquetransaction identifier in computer memory;

determining, by one or more computer processors, based on the age of thedata subject and the transaction, whether the data subject meets one ormore age criteria for the processing of personal data under thetransaction;

in response to determining the data subject meets the one or more agecriteria for the processing of personal data under the transaction,modifying, by one or more computer processors, the consent record toelectronically store an indication that the data subject has providedvalid consent for the transaction;

in response to determining the data subject does not meet the one ormore age criteria for the processing of personal data under thetransaction:

-   -   prompting the data subject to provide one or more contact        details for a guardian of the data subject;    -   accessing an electronic guardian registry for one or more data        subjects;    -   determining, based at least in part on the one or more contact        details for the guardian of the data subject using the        electronic guardian registry, that the data subject has an        identified registered guardian; and    -   communicating with the identified guardian, via the one or more        contact details, to receive the valid consent to fulfill the        transaction on behalf of the data subject by:    -   transmitting an electronic message to the identified guardian;        and    -   prompting the identified guardian to provide the valid consent        via the electronic message.        2. The computer-implemented data processing method of Concept 1,        in any embodiment described herein, may comprise:

receiving a request from a data system associated with the entity toprocess a new piece of personal data associated with the data subject aspart of the transaction;

in response to receiving the request to process the new piece ofpersonal data, determining whether the consent record comprises theindication of valid consent;

in response to determining that the consent record comprises theindication of valid consent, automatically processing the new piece ofpersonal data; and

in response to determining that the consent record does not comprise theindication of valid consent, automatically ceasing processing of the newpiece of personal data

3. The computer-implemented data processing method of Concept 2, in anyembodiment described herein, may comprise:

receiving the valid consent from the identified guardian; and

in response to receiving the valid consent from the identified guardian,modifying the consent record to electronically store an indication thatthe identified guardian has provided the valid consent for thetransaction.

4. The computer-implemented data processing method of Concept 2,wherein:

the electronic message comprises a unique code; and

the computer-implemented data processing method, in any embodimentdescribed herein, may comprise:

-   -   prompting the data subject to provide the unique code;    -   receiving the unique code from the data subject; and    -   in response to receiving the unique code from the data subject,        modifying the consent record to electronically store an        indication that the identified guardian has provided the valid        consent for the transaction.        5. The computer-implemented data processing method of Concept 4,        wherein the computer-implemented data processing method, in any        embodiment described herein, may comprise:

generating the unique code;

determining an expiration time for the unique code;

in response to receiving the unique code from the data subject,determining whether the expiration time has elapsed;

in response to determining that the expiration time has elapsed:

-   -   terminating the unique code;    -   generating and displaying a message to the data subject        indicating that the unique code has expired; and    -   modifying the consent record to electronically store an        indication that the identified guardian has not provided the        valid consent for the transaction.        6. The computer-implemented data processing method of Concept 2,        wherein the computer-implemented data processing method, in any        embodiment described herein, may comprise:

receiving the valid consent from the identified guardian, the validconsent comprising:

-   -   consent to fulfill the transaction on behalf of the data        subject; and    -   consent to fulfill one or more additional transactions on behalf        of the data subject;

in response to receiving the valid consent from the identified guardian:

-   -   modifying the consent record to electronically store an        indication that the identified guardian has provided the valid        consent for the transaction; and    -   storing an electronic indication associated with the unique        subject identifier of the consent to fulfill one or more        additional transactions on behalf of the data subject.        7. The computer-implemented data processing method of Concept 6,        wherein the computer-implemented data processing method, in any        embodiment described herein, may comprise:

receiving a second request to initiate a second transaction between theentity and the data subject;

in response to receiving the second request, generating, by a consentreceipt management system, a second unique consent receipt key;

electronically storing the unique subject identifier, the second uniqueconsent receipt key, a unique second transaction identifier, and theconsent to fulfill one or more additional transactions on behalf of thedata subject associated with the second transaction in a second consentrecord; and

electronically associating the unique subject identifier, the secondunique consent receipt key, and the unique second transaction identifierin computer memory.

8. The computer-implemented data processing method of Concept 7, whereinthe computer-implemented data processing method, in any embodimentdescribed herein, may comprise:

receiving a request from the data system associated with the entity toprocess a second new piece of personal data associated with the datasubject as part of the second transaction;

in response to receiving the request to process the second new piece ofpersonal data, determining whether the consent record comprises a secondindication of valid consent based at least in part on the consent tofulfill one or more additional transactions on behalf of the datasubject;

in response to determining that the consent record comprises the secondindication of valid consent, automatically processing the second newpiece of personal data.

9. The computer-implemented data processing method of Concept 6, whereinthe computer-implemented data processing method, in any embodimentdescribed herein, may comprise:

receiving a third request to initiate a third transaction between theentity and the data subject, the third request comprising the uniquesubject identifier;

in response to receiving the third request, generating, by a consentreceipt management system, a third unique consent receipt key;

electronically storing the unique subject identifier, the third uniqueconsent receipt key, and a unique third transaction identifier, in athird consent record;

electronically associating the unique subject identifier, the thirdunique consent receipt key, and the unique third transaction identifierin computer memory; and

determining, based at least in part on the unique subject identifier,whether a guardian associated with the data subject has previouslyprovided the consent to fulfill one or more additional transactions onbehalf of the data subject; and

in response to determining that the guardian associated with the datasubject has previously provided the consent to fulfill one or moreadditional transactions on behalf of the data subject, modifying thethird consent record to electronically store an indication of a thirdvalid consent.

10. A computer-implemented data processing method for managing a consentreceipt under a transaction, according to various embodiments,comprises:

providing, by one or more computer processors, at the consent capturepoint, a user interface for initiating a transaction between an entityand a data subject, the transaction involving processing personal dataof the data subject by the entity;

receiving, by one or more computer processors, a request to initiate thetransaction between the entity and the data subject;

in response to receiving the request, generating, by one or morecomputer processors, by a consent receipt management system, a uniqueconsent receipt key;

receiving, by one or more computer processors, from the data subject, aunique subject identifier;

requesting, by one or more computer processors, from the data subject,at least one piece of identifying information;

receiving, by one or more computer processors, the at least one piece ofidentifying information from the data subject;

determining, by one or more computer processors, based at least in parton the at least one piece of identifying information, an age of the datasubject;

identifying, by one or more computer processors, a capture pointidentifier associated with the capture point;

electronically storing, by one or more computer processors, the uniquesubject identifier, the unique consent receipt key, the capture pointidentifier, the age of the data subject, and a unique transactionidentifier associated with the transaction in a consent record;

electronically associating the unique subject identifier, the uniqueconsent receipt key, the consent capture point identifier, the age ofthe data subject, and the unique transaction identifier in computermemory;

determining, by one or more computer processors, based on the age of thedata subject and the transaction, whether the data subject meets one ormore age criteria for the processing of personal data under thetransaction;

in response to determining the data subject meets the one or more agecriteria for the processing of personal data under the transaction,modifying, by one or more computer processors, the consent record toelectronically store an indication of valid consent comprising anindication that the data subject has provided valid consent for thetransaction;

in response to determining the data subject does not meet the one ormore age criteria for the processing of personal data under thetransaction, prompting, by one or more computer processors, a guardianassociated with the data subject to provide the valid consent;

receiving, by one or more computer processors, from the guardianassociated with the data subject, the valid consent; and

in response to receiving the valid consent from the guardian associatedwith the data subject, modifying, by one or more computer processors,the consent record to electronically store the indication of validconsent comprising an indication that the guardian has provided thevalid consent for the transaction.

11. The computer-implemented data processing method of Concept 10, inany embodiment described herein, may comprise:

receiving a request from a data system associated with the entity toprocess a new piece of personal data associated with the data subject aspart of the transaction;

in response to receiving the request to process the new piece ofpersonal data, determining whether the consent record comprises theindication of valid consent;

in response to determining that the consent record comprises theindication of valid consent, automatically processing the new piece ofpersonal data; and

in response to determining that the consent record does note comprisethe indication of valid consent, automatically ceasing processing of thenew piece of personal data

12. The computer-implemented data processing method of Concept 10,wherein:

prompting the guardian associated with the data subject to provide thevalid consent comprises transmitting an electronic message to theguardian;

13. The computer-implemented data processing method of Concept 12,wherein:

the electronic message comprises a unique code; and

the computer-implemented data processing method further comprises:

-   -   prompting the data subject to provide the unique code;    -   receiving the unique code from the data subject; and    -   in response to receiving the unique code from the data subject,        modifying the consent record to electronically store the        indication of valid consent comprising the indication that the        guardian has provided the valid consent for the transaction.        14. The computer-implemented data processing method of Concept        10, wherein the computer-implemented data processing method, in        any embodiment described herein, may comprise:

receiving the valid consent from the guardian, the valid consentcomprising:

-   -   consent to fulfill the transaction on behalf of the data        subject; and    -   consent to fulfill one or more additional transactions on behalf        of the data subject;

in response to receiving the valid consent from the identified guardian:

-   -   modifying the consent record to electronically store the        indication of valid consent comprising the indication that the        guardian has provided the valid consent for the transaction; and    -   storing an electronic indication associated with the unique        subject identifier of the consent to fulfill the one or more        additional transactions on behalf of the data subject.        15. The computer-implemented data processing method of Concept        14, in any embodiment described herein, may comprise:

receiving a second request to initiate a second transaction between theentity and the data subject, the second request comprising the uniquesubject identifier;

in response to receiving the second request, generating, by the consentreceipt management system, a second unique consent receipt key;

electronically storing the unique subject identifier, the second uniqueconsent receipt key, and a unique second transaction identifier, in asecond consent record;

electronically associating the unique subject identifier, the secondunique consent receipt key, and the unique second transaction identifierin computer memory;

determining, based at least in part on the unique subject identifier,whether a guardian associated with the data subject has previouslyprovided the consent to fulfill the one or more additional transactionson behalf of the data subject; and

in response to determining that the guardian associated with the datasubject has previously provided the consent to fulfill the one or moreadditional transactions on behalf of the data subject, modifying thesecond consent record to electronically store an indication of a secondvalid consent.

16. The computer-implemented data processing method of Concept 15,wherein the computer-implemented data processing method, in anyembodiment described herein, may comprise:

receiving a request from the data system associated with the entity toprocess a second new piece of personal data associated with the datasubject as part of the second transaction;

in response to receiving the request to process the second new piece ofpersonal data, determining whether the consent record comprises theindication of the second valid consent based at least in part on theconsent to fulfill the one or more additional transactions on behalf ofthe data subject;

in response to determining that the consent record comprises theindication of the second valid consent automatically processing thesecond new piece of personal data.

17. A consent receipt management system, in any embodiment describedherein, may comprise:

one or more processors; and

computer memory that stores a plurality of consent records associatedwith a unique subject identifier, each of the plurality of consentrecords being associated with a respective transaction of a plurality oftransactions involving a data subject and an entity, wherein the consentreceipt management system is configured for:

-   -   receiving, at a particular consent capture point, a request to        initiate a transaction between the entity and the data subject,        the transaction involving collection or processing of personal        data associated with the data subject by the entity as part of a        processing activity undertaken by the entity that the data        subject is consenting to as part of the transaction;    -   in response to receiving the request:        -   identifying a transaction identifier associated with the            transaction;        -   identifying a capture point identifier for the particular            consent capture point;        -   generating, a unique consent receipt key for the            transaction; and        -   determining a unique subject identifier for the data            subject;        -   requesting, from the data subject, at least one piece of            identifying information;        -   receiving the at least one piece of identifying information            from the data subject;        -   determining, based at least in part on the at least one            piece of identifying information, an age of the data            subject;        -   electronically storing the unique subject identifier, the            unique consent receipt key, the capture point identifier,            the age of the data subject, and the transaction identifier            in computer memory;        -   electronically associating the unique subject identifier,            the unique consent receipt key, the capture point            identifier, the age of the data subject, and the transaction            identifier;        -   generating a consent record for the transaction, the consent            record comprising at least the unique subject identifier,            the age of the data subject, and the unique consent receipt            key;

receiving an indication that a data system associated with the entityhas processed a new piece of personal data associated with the datasubject as part of the transaction;

in response to receiving the indication that the data system associatedwith the entity has processed the new piece of personal data,determining, based on the age of the data subject and the transaction,whether the data subject meets one or more age criteria for theprocessing of data under the transaction;

in response to determining that the data subject meets the one or moreage criteria, automatically processing the new piece of personal data;and

in response to determining that the data subject does not meet the oneor more age criteria, automatically taking an action selected from thegroup consisting of:

-   -   automatically ceasing processing of the new piece of personal        data; and    -   prompting the data subject to provide one or more contact        details for a guardian of the data subject.        18. The consent receipt management system of Concept 17, wherein        determining, based at least in part on the at least one piece of        identifying information, the age of the data subject may        comprise:

accessing, via one or more computer networks, one or more third-partydata aggregation systems; and

determining, based at least in part on the at least one piece ofidentifying information using the one or more third-party dataaggregation systems, the age of the data subject.

19. The consent receipt management system of Concept 17, wherein:

the at least one piece of identifying information comprises the age ofthe data subject; and

the consent receipt management system is configured for:

-   -   prompting the data subject to provide a response to each of one        or more questions;    -   receiving the response to each of the one or more questions from        the data subject;    -   confirming the age of the data subject based at least in part on        the response to each of the one or more questions.        20. The consent receipt management system of Concept 17, wherein        the consent receipt management system, in any embodiment        described herein, may be configured for:

accessing an electronic guardian registry for one or more data subjects;

determining, based at least in part on the one or more contact detailsfor the guardian of the data subject using the electronic guardianregistry, that the data subject has an identified registered guardian;and

communicating with the identified guardian, via the one or more contactdetails, to receive valid consent to fulfill the transaction on behalfof the data subject by:

-   -   transmitting an electronic message to the identified guardian;        and    -   prompting the identified guardian to provide the valid consent        via the electronic message.

Various other embodiments of the system, such as any embodimentdescribed herein, may further include one or more features described inthe listing of concepts below:

1. A computer-implemented data processing method for an organization toretain one or more pieces of personal data that have a legal basis forretention, in any embodiment described herein, may comprise:

identifying one or more pieces of personal data associated with a datasubject based at least in part on one or more triggering actions;

identifying a storage location of each of the one or more pieces ofpersonal data associated with the data subject;

in response to identifying the storage location of each of the one ormore pieces of personal data associated with the data subject,automatically determining that a first portion of the one or more of thepieces of personal data has one or more legal bases for continuedstorage;

in response to determining that the first portion of the one or more ofthe pieces of personal data associated with the data subject has one ormore legal bases for continued storage, automatically maintainingstorage of the first portion of the one or more pieces of personal data;and

automatically facilitating deletion of a second portion of the one ormore pieces of personal data associated with the data subject, whereinthe second portion of the one or more pieces of personal data associatedwith the data subject is different from the first portion of the one ormore pieces of personal data.

2. The computer-implemented data processing method of claim 1, furthercomprising:

notifying the data subject that the second portion of the one or morepieces of the personal data is deleted.

3. The computer-implemented data processing method of concept 1, whereinthe one or more triggering actions is a data subject access requestsubmitted by the data subject.4. The computer-implemented data processing method of concept 1, furthercomprising:

applying one or more storage attributes to the first portion of the oneor more pieces of personal data; and

determining whether to maintain storage of the first portion of the oneor more pieces of personal data based at least in part on the applyingthe one or more storage attribute to the first portion of the one ormore pieces of personal data.

5. The computer-implemented data processing method of concept 4, whereinthe one or more storage attributes comprises a storage time of the oneor more pieces of personal data, and the method further comprising:

comparing the storage time of the one or more pieces of personal data toan authorized storage time for the organization to store the one or morepieces of personal data;

determining that the storage time of the one or more pieces of personaldata is greater than the authorized storage time for the organization tostore the one or more pieces of personal data; and

in response to determining that the storage time of the one or morepieces of personal data is greater than the authorized storage time forthe organization to store the one or more pieces of personal data,automatically notifying one or more privacy officers.

6. The computer-implemented data processing method of concept 5, furthercomprising:

in response to determining that the storage time of the one or morepieces of personal data is greater than the authorized storage time forthe organization to store the one or more pieces of personal data,automatically facilitating deletion of the first portion of the one ormore pieces of personal data associated with the data subject.

7. The computer-implemented data processing method of concept 4, whereinthe one or more storage attributes comprises a relevancy attribute ofthe one or more pieces of personal data, and the method furthercomprising:

determining that a privacy campaign associated with the one or morepieces of personal data is inactive;

in response to determining that a privacy campaign associated with theone or more pieces of personal data is inactive, automaticallyfacilitating deletion of the first portion of the one or more pieces ofpersonal data associated with the data subject.

8. The computer-implemented method of claim 1, wherein the one or morelegal bases for continued storage are selected from a group consistingof:

an ongoing legal case where the one or more pieces of personal data areto be retained;

consent from the data subject for the continued storage of the one ormore pieces of personal data; and

an indication provided by the organization that the one or more piecesof personal data are a part of anonymized data.

9. The computer-implemented method of concept 1, further comprising:

providing the first portion of the one or more of the pieces of personaldata associated with the data subject has one or more legal bases forcontinued storage to one or more privacy officers of the organization;and

receiving storage retention feedback from the one or more privacyofficers associated with the first portion of the one or more of thepieces of personal data associated with the data subject.

10. The computer-implemented method of concept 9, wherein the storageretention feedback further comprises:

a selection of a first set of the first portion of the one or morepieces of personal data for which to maintain continued storage; and

automatically facilitating deletion of a second set of the first portionof the one or more pieces of personal data associated with the datasubject.

11. A computer-implemented data processing method for an organization toretain one or more pieces of personal data that have a legal basis forretention, the method comprising:

identifying one or more pieces of personal data associated with a datasubject based at least in part on one or more triggering actions;

identifying a storage location of each of the one or more pieces ofpersonal data associated with the data subject;

in response to identifying the storage location of each of the one ormore pieces of personal data associated with the data subject,automatically determining that a first portion of the one or more of thepieces of personal data has one or more legal bases for continuedstorage;

in response to determining that the first portion of the one or more ofthe pieces of personal data associated with the data subject has one ormore legal bases for continued storage, automatically notifying one ormore privacy officers of the organization of (i) the first portion ofthe one or more pieces of personal data, and (ii) the one or more legalbases for continued storage of the first portion of the one or morepieces of personal data; and

automatically facilitating deletion of a second portion of the one ormore pieces of personal data associated with the data subject, whereinthe second portion of the one or more pieces of personal data associatedwith the data subject is different from the first portion of the one ormore pieces of personal data.

12. The computer-implemented data processing method of concept 11,further comprising:

notifying the data subject that the second portion of the one or morepieces of the personal data is deleted.

13. The computer-implemented data processing method of concept 11,wherein the one or more triggering actions is a data subject accessrequest submitted by the data subject.14. The computer-implemented data processing method of concept 11,further comprising:

applying one or more storage attributes to the first portion of the oneor more pieces of personal data; and

determining whether to maintain storage of the first portion of the oneor more pieces of personal data based at least in part on the applyingthe one or more storage attribute to the first portion of the one ormore pieces of personal data.

15. The computer-implemented data processing method of concept 14,wherein the one or more storage attributes comprises a storage time ofthe one or more pieces of personal data, and the method furthercomprising:

comparing the storage time of the one or more pieces of personal data toan authorized storage time for the organization to store the one or morepieces of personal data;

determining that the storage time of the one or more pieces of personaldata is greater than the authorized storage time for the organization tostore the one or more pieces of personal data; and

in response to determining that the storage time of the one or morepieces of personal data is greater than the authorized storage time forthe organization to store the one or more pieces of personal data,automatically notifying one or more privacy officers.

16. The computer-implemented data processing method of concept 15,further comprising:

in response to determining that the storage time of the one or morepieces of personal data is greater than the authorized storage time forthe organization to store the one or more pieces of personal data,automatically facilitating deletion of the first portion of the one ormore pieces of personal data associated with the data subject.

17. The computer-implemented data processing method of concept 14,wherein the one or more storage attributes comprises a relevancyattribute of the one or more pieces of personal data, and the methodfurther comprising:

determining that a privacy campaign associated with the one or morepieces of personal data is inactive;

in response to determining t that a privacy campaign associated with theone or more pieces of personal data is inactive, automaticallyfacilitating deletion of the first portion of the one or more pieces ofpersonal data associated with the data subject.

18. The computer-implemented method of concept 11, wherein the one ormore legal bases for continued storage are selected from a groupconsisting of:

an ongoing legal case where the one or more pieces of personal data areto be retained;

consent from the data subject for the continued storage of the one ormore pieces of personal data; and

an indication provided by the organization that the one or more piecesof personal data are a part of anonymized data.

19. A computer-implemented data processing method for an organization toretain one or more pieces of personal data that have a legal basis forretention, in some embodiments, comprises:

identifying one or more pieces of personal data associated with a datasubject based at least in part on one or more triggering actions;

automatically determining that a first portion of the one or more of thepieces of personal data has one or more legal bases for continuedstorage;

in response to determining that the first portion of the one or more ofthe pieces of personal data associated with the data subject has one ormore legal bases for continued storage, automatically maintainingstorage of the first portion of the one or more pieces of personal data;

providing the first portion of the one or more of the pieces of personaldata associated with the data subject has one or more legal bases forcontinued storage to one or more privacy officers of the organization;

receiving storage retention feedback from the one or more privacyofficers associated with the first portion of the one or more of thepieces of personal data associated with the data subject; and

automatically facilitating deletion of a second portion of the one ormore pieces of personal data associated with the data subject, whereinthe second portion of the one or more pieces of personal data associatedwith the data subject is different from the first portion of the one ormore pieces of personal data.

20. The computer-implemented method of concept 19, wherein the storageretention feedback further comprises:

a selection of a first set of the first portion of the one or morepieces of personal data for which to maintain continued storage; and

automatically facilitating deletion of a second set of the first portionof the one or more pieces of personal data associated with the datasubject.

Various other embodiments of the system, such as any embodimentdescribed herein, may further include one or more features described inthe listing of concepts below:

1. A computer-implemented data processing method for managing a consentreceipt under a transaction, in particular embodiments, comprises:

receiving a request to initiate a transaction between the entity and thedata subject;

providing, at the user interface, a privacy policy associated with theentity and based at least in part on the request to initiate thetransaction between the entity and the data subject;

accessing the privacy policy associated with the entity and based atleast in part on the request to initiate the transaction between theentity and the data subject;

storing one or more provisions of the privacy policy associated with theentity and based at least in part on the request to initiate thetransaction between the entity and the data subject;

providing a user interface for consenting to the privacy policyassociated with the entity and based at least in part on the request toinitiate the transaction between the entity and the data subject;

receiving a selection to consent to the privacy policy associated withthe entity and based at least in part on the request to initiate thetransaction between the entity and the data subject;

in response to the selection, generating, by a third-party consentreceipt management system, a consent receipt to the data subject,wherein the consent receipt includes the stored one or more provision ofthe privacy policy; and storing, by the third-party consent receiptmanagement system, the generated consent receipt.

2. The computer-implemented data processing method of concept 1, furthercomprising:

capturing one or more pieces of interaction data based at least in parton the data subject's interaction with the user interface for consentingto the privacy policy; and

storing the one or more pieces of interaction data with the generatedconsent receipt.

3. The computer-implemented data processing method of concept 2, whereinthe one or more pieces of interaction data comprises an indication ofwhether the data subject selected one or more pixels of the userinterface for consenting to the privacy policy associated with viewingthe privacy policy.4. The computer-implemented data processing method of concept 3, whereinthe one or more pieces of interaction data comprises an indication ofwhether the data subject scrolled to an ending portion of the privacypolicy within the user interface for consenting to the privacy policy.5. The computer-implemented data processing method of concept 3, whereinthe one or more pieces of interaction data comprises tracking a periodof time between (i) a first time that the data subject is presented withthe user interface for consenting to the privacy policy and (ii) asecond time that the data subject selected one or more pixels of theuser interface for consenting to the privacy policy associated withviewing the privacy policy.6. The computer-implemented data processing method of concept 3, whereinthe one or more pieces of interaction data comprises tracking a numberof data subject interactions with the user interface for consenting tothe privacy policy between (i) a first time that the data subject ispresented with the user interface for consenting to the privacy policyand (ii) a second time that the data subject selected one or more pixelsof the user interface for consenting to the privacy policy associatedwith viewing the privacy policy.7. The computer-implemented data processing method of concept 1, whereinthe accessed privacy policy includes an electronic link to the privacypolicy stored on one or more data assets of the entity.8. A computer-implemented data processing method for managing a consentreceipt under a transaction, in any embodiment described herein, maycomprise:

providing a user interface for initiating a transaction between anentity and a data subject;

receiving a request to initiate a transaction between the entity and thedata subject;

providing, at the user interface, a privacy policy associated with theentity and based at least in part on the request to initiate thetransaction between the entity and the data subject;

accessing the privacy policy associated with the entity and based atleast in part on the request to initiate the transaction between theentity and the data subject;

storing one or more provision of the privacy policy associated with theentity and based at least in part on the request to initiate thetransaction between the entity and the data subject;

providing a user interface for consenting to the privacy policyassociated with the entity and based at least in part on the request toinitiate the transaction between the entity and the data subject;

receiving a selection to consent to the privacy policy associated withthe entity and based at least in part on the request to initiate thetransaction between the entity and the data subject; and

in response to the selection, generating, by a third-party consentreceipt management system, a consent receipt to the data subject,wherein the consent receipt includes the stored one or more provision ofthe privacy policy.

9. The computer-implemented method of concept 8, further comprising:

storing, by the third-party consent receipt management system and in oneor more data assets of the entity, the generated consent receipt.

10. The computer-implemented method of concept 9, further comprising:

capturing one or more pieces of interaction data based at least in parton the data subject's interaction with the user interface for consentingto the privacy policy; and

storing the one or more pieces of interaction data with the generatedconsent receipt.

11. The computer-implemented data processing method of concept 10,wherein the one or more pieces of interaction data comprises anindication of whether the data subject scrolled to an ending portion ofthe privacy policy within the user interface for consenting to theprivacy policy.12. The computer-implemented data processing method of concept 10,wherein the one or more pieces of interaction data comprises tracking aperiod of time between (i) a first time that the data subject ispresented with the user interface for consenting to the privacy policyand (ii) a second time that the data subject selected one or more pixelsof the user interface for consenting to the privacy policy associatedwith viewing the privacy policy.13. The computer-implemented data processing method of concept 10,wherein the one or more pieces of interaction data comprises tracking anumber of data subject interactions with the user interface forconsenting to the privacy policy between (i) a first time that the datasubject is presented with the user interface for consenting to theprivacy policy and (ii) a second time that the data subject selected oneor more pixels of the user interface for consenting to the privacypolicy associated with viewing the privacy policy.14. The computer-implemented data processing method of concept 9,wherein the accessed privacy policy includes an electronic link to theprivacy policy stored on one or more data assets of the entity.15. A computer-implemented data processing method for managing a consentreceipt under a transaction, in various embodiments, comprises:

receiving a request to initiate a transaction between the entity and thedata subject;

providing, at the user interface, a privacy policy associated with theentity and based at least in part on the request to initiate thetransaction between the entity and the data subject;

accessing the privacy policy associated with the entity and based atleast in part on the request to initiate the transaction between theentity and the data subject;

providing a user interface for consenting to the privacy policyassociated with the entity and based at least in part on the request toinitiate the transaction between the entity and the data subject;

receiving a selection to consent to the privacy policy associated withthe entity and based at least in part on the request to initiate thetransaction between the entity and the data subject;

in response to the selection, generating, by a third-party consentreceipt management system, a consent receipt to the data subject,wherein the consent receipt includes the stored one or more provision ofthe privacy policy; and

storing, by the third-party consent receipt management system, thegenerated consent receipt.

16. The computer-implemented data processing method of concept 15,further comprising:

capturing one or more pieces of interaction data based at least in parton the data subject's interaction with the user interface for consentingto the privacy policy; and

storing the one or more pieces of interaction data with the generatedconsent receipt.

17. The computer-implemented data processing method of claim 15, whereinthe one or more pieces of interaction data comprises an indication ofwhether the data subject selected one or more pixels of the userinterface for consenting to the privacy policy associated with viewingthe privacy policy.18. The computer-implemented data processing method of concept 17,wherein the one or more pieces of interaction data comprises anindication of whether the data subject scrolled to an ending portion ofthe privacy policy within the user interface for consenting to theprivacy policy.19. The computer-implemented data processing method of concept 17,wherein the one or more pieces of interaction data comprises tracking aperiod of time between (i) a first time that the data subject ispresented with the user interface for consenting to the privacy policyand (ii) a second time that the data subject selected one or more pixelsof the user interface for consenting to the privacy policy associatedwith viewing the privacy policy.20. The computer-implemented data processing method of concept 17,wherein the one or more pieces of interaction data comprises tracking anumber of data subject interactions with the user interface forconsenting to the privacy policy between (i) a first time that the datasubject is presented with the user interface for consenting to theprivacy policy and (ii) a second time that the data subject selected oneor more pixels of the user interface for consenting to the privacypolicy associated with viewing the privacy policy.

Various other embodiments of the system, such as any embodimentdescribed herein, may further include one or more features described inthe listing of concepts below:

1. A computer-implemented data processing method for scanning a websiteand tracking data subject interact with the website to provide datasubject consent parameters for the website, in any embodiment describedherein, may comprise:

determining, by one or more processors, a data subject is interactingwith a particular website;

determining, by one or more processors, one or more website parametersassociated with the particular website, wherein determining the one ormore website parameters associated with the particular websitecomprises:

-   -   scanning, by one or more processors, the particular website to        determine one or more website cookies that capture data subject        information; and    -   determining, by one or more processors, a website category of        the particular website;

determining, by one or more processors, a geo-location of the datasubject when the data subject is interacting with the particularwebsite;

determining, by one or more processors, one or more data subject consentparameters based at least in part on the one or more website parametersassociated with the particular website and the geo-location of the datasubject when the data subject is interacting with the particularwebsite; and

applying, by one or more processors, the one or more data subjectconsent parameters to the data subject interaction with the particularwebsite.

2. The computer-implemented data processing method of concept 1, whereinthe method further comprises:

tracking, by one or more processors, the data subject interaction withthe particular website;

determining, by one or more processors, whether the one or more datasubject consent parameters are fulfilled;

in response to determining that the one or more data subject consentparameters are fulfilled, generating a consent receipt for the datasubject; and

transmitting the consent receipt to the data subject.

3. The computer-implemented data processing method of concept 1, whereinthe website category is based at least in part on whether the particularwebsite provides one or more targeted advertisements to the datasubject.4. The computer-implemented data processing method of concept 1, whereinscanning the particular website to determine one or more website cookiesthat capture data subject information, further comprises:

identifying one or more website cookies that capture data subjectinformation;

for each of the identified one or more website cookies,

-   -   determining one or more types of personal data captured by each        of the identified one or more website cookies; and    -   storing the one or more types of personal data captured by each        of the identified one or more website cookies.        5. The computer-implemented data processing method of concept 1,        wherein determining one or more data subject consent parameters        further comprises:

accessing one or more privacy laws associated with the geo-location ofthe data subject; and

applying the one or more privacy laws as the one or more data subjectconsent parameters.

6. The computer-implemented data processing method of concept 1, whereinthe one or more data subject consent parameters comprises at least inpart that the data subject scroll to an ending portion of a particularwebpage at the particular website for the data subject consent to beprovided by the data subject, and the method further comprises:

tracking, by one or more processors, the data subject interaction withthe particular webpage of the particular website;

determining, by one or more processors, whether the data subjectscrolled to the ending portion of a particular webpage at the particularwebsite;

in response to determining that the data subject scrolled to the endingportion of a particular webpage at the particular website, determiningthat the one or more data subject consent parameters are fulfilled; and

in response to determining that the one or more data subject consentparameters are fulfilled, generating a consent receipt for the datasubject.

7. The computer-implemented data processing method of concept 1, whereinthe one or more data subject consent parameters comprises at least inpart that the data subject select a button provided on the particularwebsite indicating that the data subject consents to the collection ofone or more pieces of personal data, and the method further comprises:

tracking, by one or more processors, the data subject interaction withthe particular webpage of the particular website;

determining, by one or more processors, whether the data subjectselected the button provided on the particular website indicating thatthe data subject consents to the collection of one or more pieces ofpersonal data;

in response to determining that the data subject selected the buttonprovided on the particular website indicating that the data subjectconsents to the collection of the one or more pieces of personal data,determining that the one or more data subject consent parameters arefulfilled; and

in response to determining that the one or more data subject consentparameters are fulfilled, generating a consent receipt for the datasubject.

8. A computer-implemented data processing method for scanning a websiteand tracking data subject interact with the website to provide datasubject consent parameters for the website, in any embodiment describedherein, may comprise:

determining, by one or more processors, a data subject is interactingwith a particular website;

determining, by one or more processors, one or more website parametersassociated with the particular website, wherein determining the one ormore website parameters associated with the particular websitecomprises:

-   -   scanning, by one or more processors, the particular website to        determine one or more website cookies that capture data subject        information;

determining, by one or more processors, a geo-location of the datasubject when the data subject is interacting with the particularwebsite;

determining, by one or more processors, one or more data subject consentparameters based at least in part on the one or more website parametersassociated with the particular website and the geo-location of the datasubject when the data subject is interacting with the particularwebsite;

tracking, by one or more processors, the data subject interaction withthe particular website;

determining, by one or more processors, whether the one or more datasubject consent parameters are fulfilled;

in response to determining that the one or more data subject consentparameters are fulfilled, generating a consent receipt for the datasubject; and

transmitting the consent receipt to the data subject.

9. The computer-implemented data processing method of concept 8, whereinthe method further comprises:

determining, by one or more processors, a website category for theparticular website, wherein website category is based at least in parton whether the particular website provides one or more targetedadvertisements to the data subject.

10. The computer-implemented data processing method of concept 8,wherein scanning the particular website to determine one or more websitecookies that capture data subject information, further comprises:

identifying one or more website cookies that capture data subjectinformation;

for each of the identified one or more website cookies,

-   -   determining one or more types of personal data captured by each        of the identified one or more website cookies; and

storing the one or more types of personal data captured by each of theidentified one or more website cookies.

11. The computer-implemented data processing method of concept 8,wherein determining one or more data subject consent parameters furthercomprises:

accessing one or more privacy laws associated with the geo-location ofthe data subject; and

applying the one or more privacy laws as the one or more data subjectconsent parameters.

12. The computer-implemented data processing method of concept 11,wherein accessing one or more privacy laws associated with thegeo-location of the data subject further comprises:

determining whether one or more updates have been applied to the one ormore privacy laws associated with the geo-location of the data subject;and

in response to determine that one or more updated have been applied tothe one or more privacy laws associated with the geo-location of thedata subject, accessing the one or more updated privacy laws associatedwith the geo-location of the data subject.

13. The computer-implemented data processing method of concept 1,wherein the one or more data subject consent parameters comprises atleast in part that the data subject scroll to an ending portion of aparticular webpage at the particular website for the data subjectconsent to be provided the data subject, and the method furthercomprises:

determining, by one or more processors, whether the data subjectscrolled to the ending portion of a particular webpage at the particularwebsite; and

in response to determining that the data subject scrolled to the endingportion of a particular webpage at the particular website, determiningthat the one or more data subject consent parameters are fulfilled.

14. The computer-implemented data processing method of concept 1,wherein the one or more data subject consent parameters comprises atleast in part that the data subject select a button provided on theparticular website indicating that the data subject consents to thecollection of one or more pieces of personal data, and the methodfurther comprises:

determining, by one or more processors, whether the data subjectselected the button provided on the particular website indicating thatthe data subject consents to the collection of one or more pieces ofpersonal data; and

in response to determining that the data subject selected the buttonprovided on the particular website indicating that the data subjectconsents to the collection of the one or more pieces of personal data,determining that the one or more data subject consent parameters arefulfilled.

15. A computer-implemented data processing method for scanning a websiteand tracking data subject interact with the website to provide datasubject consent parameters for the website, in any embodiment describedherein, may comprise:

determining, by one or more processors, a data subject is interactingwith a particular website;

determining, by one or more processors, one or more website parametersassociated with the particular website, wherein determining the one ormore website parameters associated with the particular websitecomprises:

-   -   scanning, by one or more processors, the particular website to        determine one or more website cookies that capture data subject        information; and    -   determining, by one or more processors, a website category of        the particular website;

determining, by one or more processors, a geo-location of the datasubject when the data subject is interacting with the particularwebsite;

determining, by one or more processors, one or more data subject consentparameters based at least in part on the one or more website parametersassociated with the particular website and the geo-location of the datasubject when the data subject is interacting with the particularwebsite, wherein the one or more data subject consent parameters furthercomprise one or more privacy laws associated with the geo-location ofthe data subject; and

applying, by one or more processors, the one or more data subjectconsent parameters to the data subject interaction with the particularwebsite.

16. The computer-implemented data processing method of concept 15,wherein the method further comprises:

tracking, by one or more processors, the data subject interaction withthe particular website;

determining, by one or more processors, whether the one or more datasubject consent parameters are fulfilled;

in response to determining that the one or more data subject consentparameters are fulfilled, generating a consent receipt for the datasubject; and

transmitting the consent receipt to the data subject.

17. The computer-implemented data processing method of concept 15,wherein the website category is based at least in part on whether theparticular website provides one or more targeted advertisements to thedata subject.18. The computer-implemented data processing method of concept 15,wherein scanning the particular website to determine one or more websitecookies that capture data subject information, further comprises:

identifying one or more website cookies that capture data subjectinformation;

for each of the identified one or more website cookies,

-   -   determining one or more types of personal data captured by each        of the identified one or more website cookies; and

storing the one or more types of personal data captured by each of theidentified one or more website cookies.

19. The computer-implemented data processing method of concept 15,wherein the one or more data subject consent parameters comprises atleast in part that the data subject scroll to an ending portion of aparticular webpage at the particular website for the data subjectconsent to be provided the data subject, and the method furthercomprises:

tracking, by one or more processors, the data subject interaction withthe particular webpage of the particular website;

determining, by one or more processors, whether the data subjectscrolled to the ending portion of a particular webpage at the particularwebsite;

in response to determining that the data subject scrolled to the endingportion of a particular webpage at the particular website, determiningthat the one or more data subject consent parameters are fulfilled; and

in response to determining that the one or more data subject consentparameters are fulfilled, generating a consent receipt for the datasubject

20. The computer-implemented data processing method of concept 15,wherein the one or more data subject consent parameters comprises atleast in part that the data subject select a button provided on theparticular website indicating that the data subject consents to thecollection of one or more pieces of personal data, and the methodfurther comprises:

tracking, by one or more processors, the data subject interaction withthe particular webpage of the particular website;

determining, by one or more processors, whether the data subjectselected the button provided on the particular website indicating thatthe data subject consents to the collection of one or more pieces ofpersonal data;

in response to determining that the data subject selected the buttonprovided on the particular website indicating that the data subjectconsents to the collection of the one or more pieces of personal data,determining that the one or more data subject consent parameters arefulfilled; and

in response to determining that the one or more data subject consentparameters are fulfilled, generating a consent receipt for the datasubject.

Various other embodiments of the system, such as any embodimentdescribed herein, may further include one or more features described inthe listing of concepts below:

1. A computer-implemented data processing method for determining consentuser interface validity for a provided consent user interface of a webform presenting consent information, in any embodiment described herein,may comprise:

accessing, by one or more processors, a consent user interface presentedon a web form, wherein the web form comprises consent informationpresented to a data subject completing the web form;

determining, by one or more processors, one or more configurationattributes of the consent user interface;

accessing, by one or more processors, one or more privacy regulationsassociated with presenting consent information;

comparing, by one or more processors, the one or more configurationattributes of the consent user interface to each of the one or moreprivacy regulations;

in response to comparing the one or more configuration attributes of theconsent user interface to each of the one or more privacy regulations,determining, by one or more processors, a user interface consent scoreof the consent user interface with respect to each of the one or moreprivacy regulations;

determining, by one or more processors, whether the consent userinterface is compliant with each of the one or more privacy regulations;

in response to determining that the consent user interface is notcompliant with one or more privacy regulations, flagging the consentuser interface in computer memory.

2. The computer-implemented data processing method of concept 1, whereinthe method further comprises:

in response to determining that the consent user interface is notcompliant with one or more privacy regulations, automatically modifying,by one or more processors, one or more configuration attributes of theconsent user interface; and

storing a modified consent user interface, wherein the modified consentuser interface includes the automatically modified one or moreconfiguration attributes of the consent user interface.

3. The computer-implemented data processing method of concept 1, whereinthe one or more configuration attributes is selected from a groupconsisting of:

a first selection option presented to the data subject for collection ofpersonal data of the data subject;

a detailed selection option presented to the data subject for collectionof each of one or more types of personal data of the data subject;

a position of a privacy policy within the consent user interface;

a second selection options for the data subject to be notified of one ormore particular types of personal data collected by the system; and

one or more pieces of information collected by one or more cookiesprovided in the web form.

4. The computer-implemented data processing method of concept 1, whereindetermining the user interface consent score of the consent userinterface further comprises:

for each of the one or more configuration attributes of the consent userinterface,

-   -   comparing each particular configuration attribute to the one or        more privacy regulations; and    -   calculating a configuration attribute level of compliance for        each particular configuration attribute based at least in part        on comparing the particular configuration attribute to the one        or more privacy regulations; and

calculating the user interface consent score based at least in part oneach calculated configuration attribute level of compliance.

5. The computer-implemented data processing method of concept 4, whereindetermining whether the consent user interface is compliant with each ofthe one or more privacy regulations further comprising:

comparing the user interface consent score to a threshold user interfaceconsent score determined based at least in part on each of the one ormore privacy regulations;

determining whether the user interface consent score is less than thethreshold user interface consent score; and

in response to determining that the user interface consent score is lessthan the threshold user interface consent score, determining that theconsent user interface is not compliant with the one or more privacyregulations.

6. The computer-implemented data processing method of concept 5, whereinthe threshold user interface consent score is provided by one or moreprivacy officers of an entity associated with the web form.7. The computer-implemented data processing method of concept 1, furthercomprising:

determining, by one or more processors, that one or more privacyregulation updates have been provided to the one or more privacyregulations;

in response to determining that the one or more privacy regulationupdates have been provided to the one or more privacy regulations,accessing, by one or more processors, the updated one or more privacyregulations;

comparing, by one or more processors, the one or more configurationattributes of the consent user interface to each of the one or moreupdated privacy regulations;

in response to comparing the one or more configuration attributes of theconsent user interface to each of the one or more updated privacyregulations, determining, by one or more processors, an updated userinterface consent score of the consent user interface with respect toeach of the one or more privacy regulations;

determining, by one or more processors, whether the consent userinterface is compliant with each of the one or more updated privacyregulations; and

in response to determining that the consent user interface is notcompliant with one or more updated privacy regulations, flagging theconsent user interface as non-compliant with the one or more updatedprivacy regulations.

8. The computer-implemented data processing method of concept 7, whereindetermining that one or more privacy regulation updates have beenprovided to the one or more privacy regulations further comprisesautomatically determining that one or more privacy regulation updateshave been provided to the one or more privacy regulations.9. A computer-implemented data processing method for determining consentuser interface validity for a provided consent user interface of a webform presenting consent information, in any embodiment described herein,may comprise:

accessing, by one or more processors, a consent user interface presentedon a web form, wherein the web form comprises consent informationpresented to a data subject completing the web form;

determining, by one or more processors, one or more configurationattributes of the consent user interface;

accessing, by one or more processors, one or more privacy regulationsassociated with presenting consent information;

comparing, by one or more processors, the one or more configurationattributes of the consent user interface to each of the one or moreprivacy regulations;

determining, by one or more processors, whether the consent userinterface is compliant with each of the one or more privacy regulations;

in response to determining that the consent user interface is notcompliant with one or more privacy regulations, flagging the consentuser interface.

10. The computer-implemented data processing method of concept 9,wherein the method further comprises:

in response to determining that the consent user interface is notcompliant with one or more privacy regulations, automatically modifying,by one or more processors, one or more configuration attributes of theconsent user interface; and

storing a modified consent user interface, wherein the modified consentuser interface includes the automatically modified one or moreconfiguration attributes of the consent user interface.

11. The computer-implemented data processing method of concept 9,wherein the one or more configuration attributes is selected from agroup consisting of:

a first selection option presented to the data subject for collection ofpersonal data of the data subject;

a detailed selection option presented to the data subject for collectionof each of one or more types of personal data of the data subject;

a position of a privacy policy within the consent user interface;

a second selection options for the data subject to be notified of one ormore particular types of personal data collected by the system; and

one or more pieces of information collected by one or more cookiesprovided in the web form.

12. The computer-implemented data processing method of concept 9,further comprising:

for each of the one or more configuration attributes of the consent userinterface,

-   -   comparing each particular configuration attribute to the one or        more privacy regulations, and    -   calculating a configuration attribute level of compliance for        each particular configuration attribute based at least in part        on comparing the particular configuration attribute to the one        or more privacy regulations; and

calculating a user interface consent score based at least in part oneach calculated configuration attribute level of compliance.

13. The computer-implemented data processing method of concept 12,wherein determining whether the consent user interface is compliant witheach of the one or more privacy regulations further comprising:

comparing the user interface consent score to a threshold user interfaceconsent score determined based at least in part on each of the one ormore privacy regulations;

determining whether the user interface consent score is less than thethreshold user interface consent score; and

in response to determining that the user interface consent score is lessthan the threshold user interface consent score, determining that theconsent user interface is not compliant with the one or more privacyregulations.

14. The computer-implemented data processing method of concept 13,further comprising:

determining, by one or more processors, that one or more privacyregulation updates have been provided to the one or more privacyregulations;

in response to determining that the one or more privacy regulationupdates have been provided to the one or more privacy regulations,accessing, by one or more processors, the updated one or more privacyregulations;

comparing, by one or more processors, the one or more configurationattributes of the consent user interface to each of the one or moreupdated privacy regulations;

in response to comparing the one or more configuration attributes of theconsent user interface to each of the one or more updated privacyregulations, determining, by one or more processors, an updated userinterface consent score of the consent user interface with respect toeach of the one or more privacy regulations;

determining, by one or more processors, whether the consent userinterface is compliant with each of the one or more updated privacyregulations; and

in response to determining that the consent user interface is notcompliant with one or more updated privacy regulations, flagging theconsent user interface as non-compliant with the one or more updatedprivacy regulations.

15. A data processing consent user interface validity system, in anyembodiment described herein, may comprise:

one or more computer processors;

computer memory; and

a computer-readable medium storing computer-executable instructionsthat, when executed by the one or more computer processors, cause theone or more computer processors to perform operations comprising:

-   -   accessing a consent user interface presented on a web form,        wherein the web form comprises consent information presented to        a data subject completing the web form;    -   determining one or more configuration attributes of the consent        user interface;    -   accessing one or more privacy regulations associated with        presenting consent information;    -   comparing the one or more configuration attributes of the        consent user interface to each of the one or more privacy        regulations;

in response to comparing the one or more configuration attributes of theconsent user interface to each of the one or more privacy regulations,determining a user interface consent score of the consent user interfacewith respect to each of the one or more privacy regulations;

-   -   determining whether the consent user interface is compliant with        each of the one or more privacy regulations;    -   in response to determining that the consent user interface is        not compliant with one or more privacy regulations, flagging the        consent user interface.        16. The data processing consent user interface validity system        of concept 15, further comprising:

in response to determining that the consent user interface is notcompliant with one or more privacy regulations, automatically modifyingone or more configuration attributes of the consent user interface; and

storing a modified consent user interface, wherein the modified consentuser interface includes the automatically modified one or moreconfiguration attributes of the consent user interface.

17. The data processing consent user interface validity system ofconcept 15, wherein the one or more configuration attributes is selectedfrom a group consisting of:

a first selection option presented to the data subject for collection ofpersonal data of the data subject;

a detailed selection option presented to the data subject for collectionof each of one or more types of personal data of the data subject;

a position of a privacy policy within the consent user interface;

a second selection options for the data subject to be notified of one ormore particular types of personal data collected by the system; and

one or more pieces of information collected by one or more cookiesprovided in the web form.

18. The data processing consent user interface validity system ofconcept 15, wherein determining the user interface consent score of theconsent user interface further comprises:

for each of the one or more configuration attributes of the consent userinterface,

-   -   comparing each particular configuration attribute to the one or        more privacy regulations;    -   calculating a configuration attribute level of compliance for        each particular configuration attribute based at least in part        on comparing the particular configuration attribute to the one        or more privacy regulations; and

calculating the user interface consent score based at least in part oneach calculated configuration attribute level of compliance.

19. The data processing consent user interface validity system ofconcept 18, wherein determining whether the consent user interface iscompliant with each of the one or more privacy regulations furthercomprising:

comparing the user interface consent score to a threshold user interfaceconsent score determined based at least in part on each of the one ormore privacy regulations;

determining whether the user interface consent score is less than thethreshold user interface consent score; and

in response to determining that the user interface consent score is lessthan the threshold user interface consent score, determining that theconsent user interface is not compliant with the one or more privacyregulations.

20. The data processing consent user interface validity system ofconcept 15, further comprising:

Determining that one or more privacy regulation updates have beenprovided to the one or more privacy regulations;

in response to determining that the one or more privacy regulationupdates have been provided to the one or more privacy regulations,accessing the updated one or more privacy regulations;

comparing the one or more configuration attributes of the consent userinterface to each of the one or more updated privacy regulations;

in response to comparing the one or more configuration attributes of theconsent user interface to each of the one or more updated privacyregulations, determining an updated user interface consent score of theconsent user interface with respect to each of the one or more privacyregulations;

determining whether the consent user interface is compliant with each ofthe one or more updated privacy regulations; and

in response to determining that the consent user interface is notcompliant with one or more updated privacy regulations, flagging theconsent user interface as non-compliant with the one or more updatedprivacy regulations.

Various other embodiments of the system, such as any embodimentdescribed herein, may further include one or more features described inthe listing of concepts below:

1. A computer-implemented data processing method for sharing datasubject consent data between a WebView associated with an entity and anative application associated with the entity, in any embodimentdescribed herein, may comprise:

receiving, by one or more processors, data subject consent data providedfrom a data subject at a WebView associated with an entity, the WebViewbeing within the native application;

translating, by one or more processors, the data subject consent dataprovided at the WebView associated with the entity for processing withinthe native application associated with the entity;

electronically providing, by one or more processors, the translated datasubject consent data for processing within the native applicationassociated with the entity; and

electronically providing, by one or more processors, the data subjectconsent data to the consent receipt management system for processing.

2. The computer-implemented data processing method of concept 1, furthercomprising:

storing, by one or more processors, the data subject consent dataprovided at the WebView associated with the entity.

3. The computer-implemented data processing method of concept 1, whereinreceiving the data subject consent data provided at a WebView associatedwith an entity, further comprises:

receiving one or more cookies identifying the data subject consent dataprovided at the WebView associated with the entity; and

translating the data subject consent data based on at least one value inthe one or more cookies.

4. The computer-implemented data processing method of concept 3, themethod further comprising:

accessing the at least one value in the one or more cookies;

storing the at least one value in a mobile software development kit forthe native application; and

using the at least one value to modify at least one user preferencedatabase value associated with the native application.

5. The computer-implemented data processing method of concept 3, themethod further comprising:

accessing, by the native application, the at least one value todetermine the data subject consent data for use by the application.

6. The computer-implemented data processing method of concept 5,wherein:

the WebView is a first instance of a WebView within the nativeapplication; and

the method further comprises:

receiving, at s second instance of the WebView, a request to perform asecond action requiring consent, from the data subject, for particulardata processing;

determining, based on the translated data subject consent data, whetherthe data subject has previously provided the required consent within thefirst instance of the WebView;

in response to determining that the data subject has previously providedthe required consent within the first instance of the WebView,performing the second action within the second instance of the WebView.

7. The computer-implemented data processing method of concept 6, whereinperforming the second action comprises performing the second actionwithout re-prompting the data subject to provide the consent within thesecond instance of the WebView.8. The computer-implemented data processing method of concept 6, themethod further comprising:

receiving, at the native application, a request to perform an actionrequiring consent, from the data subject, for particular dataprocessing;

determining, based on the translated data subject consent data, whetherthe data subject has previously provided the required consent within theWebView;

in response to determining that the data subject has previously providedthe required consent within the WebView, performing the action withinthe native application.

9. The computer-implemented data processing method of concept 8,wherein:

translating the data subject consent data provided at the WebViewcomprises:

-   -   setting at least one cookie for a domain loaded in the WebView;    -   extracting at least one value from the at least one cookie; and    -   storing the at least one value in a non-cookie format within the        native application; and.

electronically providing the translated data subject consent data forprocessing within the native application associated comprises storingthe at least one value in the non-cookie format within the nativeapplication locally on a computing device running the nativeapplication.

10. A computer-implemented data processing method for sharing datasubject consent data between a WebView and a native application loadingthe WebView, in any embodiment described herein, may comprise:

receiving, by one or more processors, from a data subject, within thenative application, consent to process one or more pieces of personaldata, the consent to process the one or more pieces of personal datacomprising one or more user preferences;

in response to receiving the consent to process the one or more piecesof personal data, building, by one or more processors, at least onecookie, the at least one cookie defining at least one value based atleast in part on the one or more user preferences provided with theconsent to process the one or more pieces of personal data;

receiving, by one or more processors, a request to load a particular webdomain within a WebView in the native application;

in response to receiving the request to load the particular web domainwithin the WebView in the native application:

-   -   transmitting a request to the particular web domain to load a        particular website within the WebView; and    -   setting the at least one cookie for the particular website by:        -   appending the at least one cookie to the request to load the            particular website; and        -   in response to receiving the at least one cookie at the            particular web domain, modifying at least one WebView cookie            based on the at least one value.            11. The computer-implemented data processing method of            concept 10, the method further comprising:

accessing at least one feature on the particular website within theWebView that requires the consent to process the one or more pieces ofpersonal data without re-prompting the data subject to provide theconsent to process the one or more pieces of personal data.

12. The computer-implemented data processing method of concept 11,wherein accessing the at least one feature on the particular websitewithin the WebView that requires the consent to process the one or morepieces of personal data without re-prompting the data subject to providethe consent to process the one or more pieces of personal data comprisesutilizing the consent to process the one or more pieces of personal dataprovided within the native application.13. The computer-implemented data processing method of concept 11,wherein the consent to process the one or more pieces of personal datacomprises consent to the use of the at least one cookie by theparticular web domain.14. The computer-implemented data processing method of concept 10,wherein building the at least one cookie comprises storing the at leastone cookie in a storage location selected from the group consisting of:

-   -   one or more storage locations local to a computing device        running the native application; and    -   one or more remote servers.        15. A computer-implemented data processing method for sharing        data subject consent data between a WebView associated with an        entity and a native application associated with the entity, in        any embodiment described herein, may comprise:

receiving, from a data subject, by one or more processors, data subjectconsent data provided at the native application associated with anentity;

translating, by one or more processors, the data subject consent dataprovided at the native application associated with the entity forstorage in a storage location accessible by a WebView associated withthe entity;

electronically providing, by one or more processors, the translated datasubject consent data to the storage location accessible by the WebViewassociated with the entity for processing within the WebView associatedwith the entity;

receiving, at the WebView, a request to perform an action requiringconsent, from the data subject, for particular data processing;

determining, based on the translated data subject consent data, whetherthe data subject has previously provided the required consent within thenative application;

in response to determining that the data subject has previously providedthe required consent within the native application, performing theaction within the WebView.

16. The computer-implemented data processing method of concept 15,wherein electronically providing the translated data subject consentdata to the storage location accessible by the WebView associated withthe entity for processing within the WebView associated with the entitycomprises appending the translated data subject consent data to a headerof a URL request sent from the native application to the WebView.17. The computer-implemented data processing method of concept 15, themethod comprising:

receiving, from the native application, a request to launch the WebView;and

in response to receiving the request to launch the WebView, launching,by one or more processors, the WebView in the native application.

18. The computer-implemented data processing method of concept 17,wherein:

launching the WebView in the native application comprises directing theWebView to load a particular domain within the WebView; and

translating the data subject consent data provided at the nativeapplication comprises setting at least one cookie for the domain.

19. The computer-implemented data processing method of concept 18,wherein performing the action comprises performing the action within theWebView without prompting the data subject to provide the consent withinthe WebView.20. The computer-implemented data processing method of concept 15, thestorage location is selected from the group consisting of: one or morestorage locations local to a computing device running the nativeapplication; and one or more remote servers.

A computer-implemented method for automatically blocking the use of oneor more tracking tools during the use of a website by a user, accordingto various embodiments, may include: scanning, by one or more computerprocessors, one or more webpages associated with a website to identifyone or more tracking tools associated with the one or more webpages;analyzing, by one or more computer processors, a loading of the one ormore webpages to identify one or more scripts executed during theloading of the one or more webpages; identifying, by one or morecomputer processors, based at least in part on the analysis of theloading of the one or more webpages, a respective source scriptassociated with each of the one or more tracking tools, wherein eachrespective source script invokes a respective tracking tool of the oneor more tracking tools; analyzing, by one or more computer processors,each of the one or more tracking tools to determine a categorization ofeach of the one or more tracking tools based at least in part oncomparing data associated with each of the one or more tracking tools toknow tracking tool data; generating, by one or more computer processors,a computer-readable file comprising an indicator of each of the one ormore tracking tools, an indicator of the respective source scriptassociated with each of the one or more tracking tools, and an indicatorof the categorization of each of the one or more tracking tools;storing, by one or more computer processors in a computer memory, thecomputer-readable file; generating, by one or more computer processors,a tracking tool blocking script comprising a subset of thecomputer-readable file; executing, by one or more computer processors,the tracking tool blocking script in response to detecting a requestfrom a user to load the one or more webpages; determining, by one ormore computer processors, based at least in part on executing thetracking tool blocking script, whether a particular script of the one ormore scripts is authorized to execute on the one or more webpages; andat least partially in response to determining that the particular scriptof the one or more scripts is not authorized to execute on the one ormore webpages, blocking, by one or more computer processors, based atleast in part on executing the tracking tool blocking script, theparticular script from executing on the one or more webpages.

In particular embodiments, determining whether the particular script isauthorized to execute on the one or more webpages comprises determining,based at least in part on executing the tracking tool blocking script,that the user has not provided consent for use of a particular trackingtool of the one or more tracking tools associated with the particularscript. In particular embodiments, the method may also includegenerating, by one or more computer processors, a prompt requestingconsent from the user for use of the particular tracking tool. Inparticular embodiments, determining that the user has not providedconsent for the particular tracking tool comprises: determining, by oneor more computer processors executing the tracking tool blocking script,based at least in part on the subset of the computer-readable file, aparticular category for the particular tracking tool; and determining,by one or more computer processors executing the tracking tool blockingscript, that the user has not provided consent for tracking toolsassociated with the particular category. In particular embodiments, themethod may also include generating, by one or more computer processors,a prompt requesting consent from the user for use of the tracking toolsassociated with the particular category. In particular embodiments, thecomputer-readable file is a JavaScript Object Notation (JSON) file. Inparticular embodiments, generating the tracking tool blocking scriptcomprising the subset of the computer-readable file comprises embedding,by one or more computer processors, the JSON file in the tracking toolblocking script.

An automatic tracking tool blocking system, according to variousembodiments, may include: one or more computer processors; and computermemory storing computer-executable instructions that, when executed bythe one or more computer processors, cause the one or more computerprocessors to perform one or more operations comprising: identifying oneor more tracking tools associated with the one or more webpages;analyzing one or more data flows generated during a loading of the oneor more webpages to identify one or more scripts; identifying, based atleast in part on the analysis of the one or more data flows, aparticular script of the one or more scripts as a particular sourcescript for a particular tracking tool of the one or more tracking tools;accessing a database of known tracking tool data; using the database ofknown tracking tool data to determine a categorization for theparticular tracking tool based at least in part on the particulartracking tool and the particular source script; generating one or morepieces of tracking tool analysis computer code; embedding an indicatorof the particular tracking tool, an indicator of the particular sourcescript, and an indicator of the categorization for the particulartracking tool in the one or more pieces of tracking tool analysis code;detecting a subsequent loading of the one or more webpages; at leastpartially in response to detecting the subsequent loading of the one ormore webpages, executing the one or more pieces of tracking toolanalysis computer code; at least partially in response to executing theone or more pieces of tracking tool analysis computer code, identifyingthe particular tracking tool on the one or more webpages during thesubsequent loading of the one or more webpages; at least partially inresponse to identifying the particular tracking tool on the one or morewebpages during the subsequent loading of the one or more webpages,tagging the particular tracking tool on the one or more webpages withthe categorization; and determining whether to execute the particularsource script during the subsequent loading of the one or more webpagesbased at least in part on the categorization.

In particular embodiments, analyzing the one or more data flowscomprises analyzing one or more response headers received from one ormore respective remote systems to identify the one or more scripts.Identifying, based at least in part on the analysis of the one or moredata flows, the particular script as the particular source script forthe particular tracking tool may be based at least in part on theanalysis of the one or more response headers. In particular embodiments,determining whether to execute the particular source script during thesubsequent loading of the one or more webpages based at least in part onthe categorization comprises determining whether a user has providedconsent for tracking tools associated with the categorization. Inparticular embodiments, the one or more operations may also include: atleast partially in response to determining that the user has notprovided consent for the tracking tools associated with thecategorization, prompting the user for consent from the user for use ofthe tracking tools associated with the categorization; receiving consentfrom the user for use of the tracking tools associated with thecategorization; and at least partially in response to receiving consentfrom the user for use of the tracking tools associated with thecategorization, allowing the particular source script to execute duringthe subsequent loading of the one or more webpages. In particularembodiments, the one or more operations may also include: at leastpartially in response to determining that the user has not providedconsent for the tracking tools associated with the categorization,prompting the user for consent from the user for use of the trackingtools associated with the categorization; receiving a denial of consentfrom the user for use of the tracking tools associated with thecategorization; and at least partially in response to receiving thedenial of consent from the user for use of the tracking tools associatedwith the categorization, preventing the particular source script fromexecuting during the subsequent loading of the one or more webpages. Thecategorization may be associated with one or more types of personal dataprocessed by the particular tracking tool.

A non-transitory computer-readable medium, according to variousembodiments, may store computer-executable instructions forautomatically blocking tracking tools by: loading, by one or morecomputer processors, one or more webpages; during the loading of the oneor more webpages: identifying, by one or more computer processors, oneor more tracking tools associated with the one or more webpages;analyzing, by one or more computer processors, the loading of the one ormore webpages to identify one or more scripts executed during theloading of the one or more webpages; and determining, by one or morecomputer processors, based at least in part on the analysis of theloading of the one or more webpages, that a particular script of the oneor more scripts is a source script for a particular tracking tool of theone or more tracking tools by determining that the particular scriptinvokes the particular tracking tool during the loading of the one ormore webpages; comparing, by one or more computer processors, the sourcescript and the particular tracking tool to known tracking tool data;determining, by one or more computer processors, based at least in parton the comparison of the source script and the particular tracking toolto known tracking tool data, a corresponding known tracking tool;determining, by one or more computer processors; based at least in parton the known tracking tool data, a categorization for the known trackingtool; assigning, by one or more computer processors, the categorizationfor the known tracking tool to the source script; detecting, by one ormore computer processors, a subsequent loading of the one or morewebpages; and preventing, by one or more computer processors, based atleast in part on the categorization assigned to the source script, thesource script from executing during the subsequent loading of the one ormore webpages.

In particular embodiments, assigning the categorization to the sourcescript may include: storing, by one or more computer processors in acomputer memory, a data structure comprising an indication of the sourcescript and an indication of the categorization; and associating, by oneor more computer processors in the computer memory, the source scriptand the categorization. In particular embodiments, storing the datastructure may include storing the data structure as embedded data in oneor more pieces of JavaScript code. The computer-executable instructionsmay also instructions for tagging, by one or more computer processors,during the subsequent loading of the one or more webpages, the sourcescript with the indication of the categorization. In particularembodiments, the categorization is associated with user consent for useof the particular tracking tool. In particular embodiments, thecomputer-executable instructions may include instructions for promptinga user for consent to use the particular tracking tool.

The details of one or more embodiments of the subject matter describedin this specification are set forth in the accompanying drawings and thedescription below. Other features, aspects, and advantages of thesubject matter may become apparent from the description, the drawings,and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of a data subject access request fulfillment systemare described below. In the course of this description, reference willbe made to the accompanying drawings, which are not necessarily drawn toscale, and wherein:

FIG. 1 depicts a data model generation and population system accordingto particular embodiments.

FIG. 2 is a schematic diagram of a computer (such as the data modelgeneration server 110, or data model population server 120) that issuitable for use in various embodiments of the data model generation andpopulation system shown in FIG. 1 (e.g., or the consent interfacemanagement server 6110, or one or more remote computing devices 6150)that is suitable for use in various embodiments of the consentconversion optimization system shown in FIG. 60).

FIG. 3 is a flowchart showing an example of steps performed by a DataModel Generation Module according to particular embodiments.

FIGS. 4-10 depict various exemplary visual representations of datamodels according to particular embodiments.

FIG. 11 is a flowchart showing an example of steps performed by a DataModel Population Module.

FIG. 12 is a flowchart showing an example of steps performed by a DataPopulation Questionnaire Generation Module.

FIG. 13 is a process flow for populating a data inventory according to aparticular embodiment using one or more data mapping techniques.

FIGS. 14-25 depict exemplary screen displays and graphical userinterfaces (GUIs) according to various embodiments of the system, whichmay display information associated with the system or enable access to,or interaction with, the system by one or more users (e.g., to configurea questionnaire for populating one or more inventory attributes for oneor more data models, complete one or more assessments, etc.).

FIG. 26 is a flowchart showing an example of steps performed by anIntelligent Identity Scanning Module.

FIG. 27 is schematic diagram of network architecture for an intelligentidentity scanning system 2700 according to a particular embodiment.

FIG. 28 is a schematic diagram of an asset access methodology utilizedby an intelligent identity scanning system 2700 in various embodimentsof the system.

FIG. 29 is a flowchart showing an example of a processes performed by aData Subject Access Request Fulfillment Module 2900 according to variousembodiments.

FIGS. 30-31 depict exemplary screen displays and graphical userinterfaces (GUIs) according to various embodiments of the system, whichmay display information associated with the system or enable access to,or interaction with, the system by one or more users (e.g., for thepurpose of submitting a data subject access request or other suitablerequest).

FIGS. 32-35 depict exemplary screen displays and graphical userinterfaces (GUIs) according to various embodiments of the system, whichmay display information associated with the system or enable access to,or interaction with, the system by one or more users (e.g., for thepurpose of flagging one or more risks associated with one or moreparticular questionnaire questions).

FIG. 36 depicts a schematic diagram of a centralized data repositorysystem according to particular embodiments of the present system.

FIG. 37 is a flowchart showing an example of a processes performed by adata repository module according to various embodiments, which may, forexample, be executed by the centralized data repository system of FIG.36.

FIG. 38 depicts a schematic diagram of a consent receipt managementsystem according to particular embodiments.

FIGS. 39-54 are computer screen shots that demonstrate the operation ofvarious embodiments.

FIG. 55 depicts an exemplary consent receipt management system accordingto particular embodiments.

FIG. 56 is a flow chart showing an example of a process performed by aConsent Receipt Management Module 5600 according to particularembodiments.

FIG. 57 is a flow chart showing an example of a process performed by aConsent Expiration and Re-Triggering Module 5700 according to particularembodiments.

FIG. 58 depicts an exemplary screen display and graphical user interface(GUI) according to various embodiments of the system, which may displayinformation associated with the system or enable access to, orinteraction with, the system by one or more users (e.g., for the purposeof analyzing one or more consent conversion analytics).

FIG. 59 is a flow chart showing an example of a process performed by aConsent Validity Scoring Module 5900 according to particularembodiments.

FIG. 60 depicts an exemplary consent conversion optimization systemaccording to particular embodiments.

FIG. 61 is a flow chart showing an example of a process performed by aConsent Conversion Optimization Module according to particularembodiments.

FIGS. 62-70 depict exemplary screen displays and graphical userinterfaces (GUIs) for enabling a user (e.g., of a particular website) toinput consent preferences. These exemplary user interfaces may include,for example, one or more user interfaces that the consent conversionoptimization system is configured to test against one another todetermine which particular user interface results in a higher rate ofconsent provided by users.

FIGS. 71-75 depict exemplary screen displays and graphical userinterfaces (GUIs) for enabling a user (e.g., an administrator of aparticular webpage or website) to generate and implement one or more newconsent interface tests, review existing consent interface tests, etc.These exemplary user interfaces may include, for example, one or moreuser interfaces that enable a user to initiate one or more sets of newtest interfaces within the context of a consent conversion optimizationsystem as described herein.

FIG. 76 depicts an exemplary consent conversion optimization systemaccording to particular embodiments.

FIG. 77 is a flow chart showing an example of a process performed by aConsent Refresh Module according to particular embodiments.

FIG. 78 is a flow chart showing an example of a process performed by aConsent Re-Prompt Module according to particular embodiments.

FIG. 79 is user interface according to a particular embodiment depictingtransaction data for a particular data subject.

FIG. 80 depicts an exemplary user interface monitoring system accordingto particular embodiments.

FIG. 81 is a flow chart showing an example of a process performed by aUser Interface Monitoring Module according to particular embodiments.

FIGS. 82-85 depict exemplary user interfaces according to variousembodiments of the system, which may, for example, enable a user toaccess various system features related to consent capture points andinterfaces.

FIG. 86 is a flow chart showing an example of a process performed by aConsent Confirmation and Process Blocking Module according to particularembodiments.

FIG. 87 depicts exemplary native application data processing consentsharing modules according to various embodiments.

FIG. 88 depicts an exemplary data processing consent sharing systemaccording to various embodiments.

FIG. 89 depicts an exemplary data processing consent sharing systemaccording to particular embodiments.

FIG. 90 is a flow chart showing an example of a process performed by aPersonal Data Receipt Module according to particular embodiments.

FIG. 91 is a flow chart showing an example of a process performed by aPersonal Data Consent Verification Module according to particularembodiments.

FIG. 92 is a flow chart showing an example of a process performed by aCookie Compliance Testing Module according to particular embodiments.

FIG. 93 is a flow chart showing an example of a process performed by aConsent User Interface Validity Module according to particularembodiments.

FIG. 94 is a flow chart showing an example of a process performed by aTracking Tool Categorization Module according to particular embodiments.

FIG. 95 is a flow chart showing an example of a process performed by anAutomatic Tracking Tool Blocking Module according to particularembodiments.

DETAILED DESCRIPTION

Various embodiments now will be described more fully hereinafter withreference to the accompanying drawings. It should be understood that theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein. Rather, theseembodiments are provided so that this disclosure will be thorough andcomplete, and will fully convey the scope of the invention to thoseskilled in the art. Like numbers refer to like elements throughout.

Overview

A data model generation and population system, according to particularembodiments, is configured to generate a data model (e.g., one or moredata models) that maps one or more relationships between and/or among aplurality of data assets utilized by a corporation or other entity(e.g., individual, organization, etc.) in the context, for example, ofone or more business processes. In particular embodiments, each of theplurality of data assets (e.g., data systems) may include, for example,any entity that collects, processes, contains, and/or transfers data(e.g., such as a software application, “internet of things” computerizeddevice, database, website, data-center, server, etc.). For example, afirst data asset may include any software or device (e.g., server orservers) utilized by a particular entity for such data collection,processing, transfer, storage, etc.

As shown in FIGS. 4 and 5, in various embodiments, the data model maystore the following information: (1) the organization that owns and/oruses a particular data asset (a primary data asset, which is shown inthe center of the data model in FIG. 4); (2) one or more departmentswithin the organization that are responsible for the data asset; (3) oneor more software applications that collect data (e.g., personal data)for storage in and/or use by the data asset (e.g., or one or more othersuitable collection assets from which the personal data that iscollected, processed, stored, etc. by the primary data asset issourced); (4) one or more particular data subjects (or categories ofdata subjects) that information is collected from for use by the dataasset; (5) one or more particular types of data that are collected byeach of the particular applications for storage in and/or use by thedata asset; (6) one or more individuals (e.g., particular individuals ortypes of individuals) that are permitted to access and/or use the datastored in, or used by, the data asset; (7) which particular types ofdata each of those individuals are allowed to access and use; and (8)one or more data assets (destination assets) that the data istransferred to for other use, and which particular data is transferredto each of those data assets. As shown in FIGS. 6 and 7, the system mayalso optionally store information regarding, for example, which businessprocesses and processing activities utilize the data asset.

In particular embodiments, the data model stores this information foreach of a plurality of different data assets and may include linksbetween, for example, a portion of the model that provides informationfor a first particular data asset and a second portion of the model thatprovides information for a second particular data asset.

In various embodiments, the data model generation and population systemmay be implemented in the context of any suitable privacy managementsystem that is configured to ensure compliance with one or more legal orindustry standards related to the collection and/or storage of privateinformation. In various embodiments, a particular organization,sub-group, or other entity may initiate a privacy campaign or otheractivity (e.g., processing activity) as part of its business activities.In such embodiments, the privacy campaign may include any undertaking bya particular organization (e.g., such as a project or other activity)that includes the collection, entry, and/or storage (e.g., in memory) ofany personal data associated with one or more individuals. In particularembodiments, a privacy campaign may include any project undertaken by anorganization that includes the use of personal data, or any otheractivity that could have an impact on the privacy of one or moreindividuals.

In any embodiment described herein, personal data may include, forexample: (1) the name of a particular data subject (which may be aparticular individual); (2) the data subject's address; (3) the datasubject's telephone number; (4) the data subject's e-mail address; (5)the data subject's social security number; (6) information associatedwith one or more of the data subject's credit accounts (e.g., creditcard numbers); (7) banking information for the data subject; (8)location data for the data subject (e.g., their present or pastlocation); (9) internet search history for the data subject; and/or (10)any other suitable personal information, such as other personalinformation discussed herein. In particular embodiments, such personaldata may include one or more cookies (e.g., where the individual isdirectly identifiable or may be identifiable based at least in part oninformation stored in the one or more cookies).

In particular embodiments, when generating a data model, the system may,for example: (1) identify one or more data assets associated with aparticular organization; (2) generate a data inventory for each of theone or more data assets, where the data inventory comprises informationsuch as: (a) one or more processing activities associated with each ofthe one or more data assets, (b) transfer data associated with each ofthe one or more data assets (data regarding which data is transferredto/from each of the data assets, and which data assets, or individuals,the data is received from and/or transferred to, (c) personal dataassociated with each of the one or more data assets (e.g., particulartypes of data collected, stored, processed, etc. by the one or more dataassets), and/or (d) any other suitable information; and (3) populate thedata model using one or more suitable techniques.

In particular embodiments, the one or more techniques for populating thedata model may include, for example: (1) obtaining information for thedata model by using one or more questionnaires associated with aparticular privacy campaign, processing activity, etc.; (2) using one ormore intelligent identity scanning techniques discussed herein toidentify personal data stored by the system and map such data to asuitable data model, data asset within a data model, etc.; (3) obtaininginformation for the data model from a third-party application (or otherapplication) using one or more application programming interfaces (API);and/or (4) using any other suitable technique.

In particular embodiments, the system is configured to generate andpopulate a data model substantially on the fly (e.g., as the systemreceives new data associated with particular processing activities). Instill any embodiment described herein, the system is configured togenerate and populate a data model based at least in part on existinginformation stored by the system (e.g., in one or more data assets), forexample, using one or more suitable scanning techniques describedherein.

As may be understood in light of this disclosure, a particularorganization may undertake a plurality of different privacy campaigns,processing activities, etc. that involve the collection and storage ofpersonal data. In some embodiments, each of the plurality of differentprocessing activities may collect redundant data (e.g., may collect thesame personal data for a particular individual more than once), and maystore data and/or redundant data in one or more particular locations(e.g., on one or more different servers, in one or more differentdatabases, etc.). In this way, a particular organization may storepersonal data in a plurality of different locations which may includeone or more known and/or unknown locations. By generating and populatinga data model of one or more data assets that are involved in thecollection, storage and processing of such personal data, the system maybe configured to create a data model that facilitates a straightforwardretrieval of information stored by the organization as desired. Forexample, in various embodiments, the system may be configured to use adata model in substantially automatically responding to one or more dataaccess requests by an individual (e.g., or other organization). Variousembodiments of a system for generating and populating a data model aredescribed more fully below.

In particular embodiments, any entity (e.g., organization, company,etc.) that collects, stores, processes, etc. personal data may requireone or more of: (1) consent from a data subject from whom the personaldata is collected and/or processed; and/or (2) a lawful basis for thecollection and/or processing of the personal data. In variousembodiments, the entity may be required to, for example: (1) demonstratethat a data subject has freely given specific, informed, and unambiguousindication of the data subject's agreement to the processing of his orher personal data (e.g., in the form of a statement or clear affirmativeaction); (2) demonstrate that the entity received consent from a datasubject in a manner clearly distinguishable from other matters (e.g., inan intelligible and easily accessible form, using clear and plainlanguage, etc.); (3) enable a data subject to withdraw consent as easilyas the data subject can give consent; (4) separate a data subject'sconsent from performance under any contract unless such processing isnecessary for performance under the contract; etc.

In various embodiments, a consent receipt management system may beimplemented in the context of any suitable privacy management systemthat is configured to ensure compliance with one or more legal orindustry standards related to the collection and/or storage of privateinformation (e.g., such as personal data). Various privacy and securitypolicies (e.g., such as the European Union's General Data ProtectionRegulation, California's California Consumer Privacy Act, and other suchpolicies) may provide data subjects (e.g., individuals, organizations,or other entities) with certain rights related to the data subject'spersonal data that is collected, stored, or otherwise processed by anorganization. These rights may include, for example: (1) a right toerasure of the data subject's personal data (e.g., in cases where nolegal basis applies to the processing and/or collection of the personaldata; (2) a right to withdraw consent to the processing and/orcollection of their personal data; (3) a right to receive the personaldata concerning the data subject, which he or she has provided to anentity (e.g., organization), in a structured, commonly used andmachine-readable format; and/or (4) any other right which may beafforded to the data subject under any applicable legal and/or industrypolicy.

In particular embodiments, the consent receipt management system isconfigured to: (1) enable an entity to demonstrate that valid consenthas been obtained for each particular data subject for whom the entitycollects and/or processes personal data; and (2) enable one or more datasubjects to exercise one or more rights described herein.

The system may, for example, be configured to track data on behalf of anentity that collects and/or processes personal data related to: (1) whoconsented to the processing or collection of personal data (e.g., thedata subject themselves or a person legally entitled to consent on theirbehalf such as a parent, guardian, etc.); (2) when the consent was given(e.g., a date and time); (3) what information was provided to theconsenter at the time of consent (e.g., a privacy policy, what personaldata would be collected following the provision of the consent, for whatpurpose that personal data would be collected, etc.); (4) how consentwas received (e.g., one or more copies of a data capture form, web form,etc. via which consent was provided by the consenter); (5) when consentwas withdrawn (e.g., a date and time of consent withdrawal if theconsenter withdraws consent); and/or (6) any other suitable data relatedto receipt or withdrawal of consent. In particular embodiments, thesystem is configured to store metadata in association with processedpersonal data that indicates one or more pieces of consent data thatauthorized the processing of the personal data.

In further embodiments, the system may be configured to provide datasubjects with a centralized interface that is configured to: (1) provideinformation regarding each of one or more valid consents that the datasubject has provided to one or more entities related to the collectionand/or processing of their personal data; (2) provide one or moreperiodic reminders regarding the data subject's right to withdrawpreviously given consent (e.g., every 6 months in the case ofcommunications data and metadata, etc.); (3) provide a withdrawalmechanism for the withdrawal of one or more previously provided validconsents (e.g., in a format that is substantially similar to a format inwhich the valid consent was given by the data subject); (4) refreshconsent when appropriate (e.g., the system may be configured to elicitupdated consent in cases where particular previously validly consentedto processing is used for a new purpose, a particular amount of time haselapsed since consent was given, etc.).

In particular embodiments, the system is configured to manage one ormore consent receipts between a data subject and an entity. In variousembodiments, a consent receipt may include a record (e.g., a data recordstored in memory and associated with the data subject) of consent, forexample, as a transactional agreement where the data subject is alreadyidentified or identifiable as part of the data processing that resultsfrom the provided consent. In any embodiment described herein, thesystem may be configured to generate a consent receipt in response to adata subject providing valid consent. In some embodiments, the system isconfigured to determine whether one or more conditions for valid consenthave been met prior to generating the consent receipt. Variousembodiments of a consent receipt management system are described morefully below.

In particular embodiments, any entity (e.g., organization, company,etc.) that collects, stores, processes, etc. personal data may requireone or more of: (1) consent from a data subject from whom the personaldata is collected and/or processed; and/or (2) a lawful basis for thecollection and/or processing of the personal data. In variousembodiments, the entity may be required to, for example: (1) demonstratethat a data subject has freely given specific, informed, and unambiguousindication of the data subject's agreement to the processing of his orher personal data (e.g., in the form of a statement or clear affirmativeaction); (2) demonstrate that the entity received consent from a datasubject in a manner clearly distinguishable from other matters (e.g., inan intelligible and easily accessible form, using clear and plainlanguage, etc.); (3) enable a data subject to withdraw consent as easilyas the data subject can give consent; (4) separate a data subject'sconsent from performance under any contract unless such processing isnecessary for performance under the contract; etc.

In particular, when storing or retrieving information from an end user'sdevice, an entity may be required to receive consent from the end userfor such storage and retrieval. Web cookies are a common technology thatmay be directly impacted by the consent requirements discussed herein.Accordingly, an entity that use cookies (e.g., on one or more webpages)may be required to use one or more banners, pop-ups or other userinterfaces on the website in order to capture consent from end-users tostore and retrieve cookie data.

The consent required to store and retrieve cookie data may, for example,require a clear affirmative act establishing a freely given, specific,informed and unambiguous indication of a data subject's agreement to theprocessing of personal data. This may include, ticking a box whenvisiting an internet website, choosing technical settings forinformation society services, or any other suitable statement or conductwhich clearly indicates in this context the data subject's acceptance ofthe proposed processing of their personal data.

In various embodiments, pre-ticked boxes (or other preselected options)or inactivity may not be sufficient to demonstrate freely given consent.For example, an entity may be unable to rely on implied consent (e.g.,“by visiting this website, you accept cookies”). Without a genuine andfree choice by data subjects and/or other end users, an entity may beunable to demonstrate valid consent (e.g., and therefore unable toutilize cookies in association with such data subjects and/or endusers).

A particular entity may use cookies for any number of suitable reasons.For example, an entity may utilize: (1) one or more functionalitycookies (which may, for example, enhance the functionality of a websiteby storing user preferences such as location for a weather or newswebsite); (2) one or more performance cookies (which may, for example,help to improve performance of the website on the user's device toprovide a better user experience); (3) one or more targeting cookies(which may, for example, be used by advertising partners to build aprofile of interests for a user in order to show relevant advertisementsthrough the website; (4) etc. Cookies may also be used for any othersuitable reason such as, for example: (1) to measure and improve sitequality through analysis of visitor behavior (e.g., through‘analytics’); (2) to personalize pages and remember visitor preferences;(3) to manage shopping carts in online stores; (4) to track peopleacross websites and deliver targeted advertising; (5) etc.

Under various regulations, an entity may not be required to obtainconsent to use every type of cookie utilized by a particular website.For example, strictly necessary cookies, which may include cookies thatare necessary for a website to function, may not require consent. Anexample of strictly necessary cookies may include, for example, sessioncookies. Session cookies may include cookies that are strictly requiredfor website functionality and don't track user activity once the browserwindow is closed. Examples of session cookies include: (1) facetedsearch filter cookies; (2) user authentication cookies; (3) cookies thatenable shopping cart functionality; (4) cookies used to enable playbackof multimedia content; (5) etc.

Cookies which may trigger a requirement for obtaining consent mayinclude cookies such as persistent cookies. Persistent cookies mayinclude, for example, cookies used to track user behavior even after theuse has moved on from a website or closed a browser window.

In order to comply with particular regulations, an entity may berequired to: (1) present visitors with information about the cookies awebsite uses and the purpose of the cookies (e.g., any suitable purposedescribed herein or other suitable purpose); (2) obtain consent to usethose cookies (e.g., obtain separate consent to use each particular typeof cookies used by the website); and (3) provide a mechanism forvisitors to withdraw consent (e.g., that is as straightforward as themechanism through which the visitors initially provided consent). In anyembodiment described herein, an entity may only need to receive validconsent from any particular visitor a single time (e.g., returningvisitors may not be required to provide consent on subsequent visits tothe site). In particular embodiments, although they may not requireexplicit consent to use, an entity may be required to notify a visitorof any strictly necessary cookies used by a website.

Because entities may desire to maximize a number of end users and otherdata subjects that provide this valid consent, it may be beneficial toprovide a user interface through which the users are more likely toprovide such consent. By receiving consent from a high number of users,the entity may, for example: (1) receive higher revenue from advertisingpartners; (2) receive more traffic to the website because users of thewebsite may enjoy a better experience while visiting the website; etc.

In particular embodiments, a consent conversion optimization system isconfigured to test two or more test consent interfaces against oneanother to determine which of the two or more consent interfaces resultsin a higher conversion percentage (e.g., to determine which of the twoor more interfaces lead to a higher number of end users and/or datasubjects providing a requested level of consent for the creation,storage and use or cookies by a particular website). The system may, forexample, analyze end user interaction with each particular test consentinterface to determine which of the two or more user interfaces: (1)result in a higher incidence of a desired level of provided consent; (2)are easier to use by the end users and/or data subjects (e.g., take lesstime to complete, require a fewer number of clicks, etc.); (3) etc.

The system may then be configured to automatically select frombetween/among the two or more test interfaces and use the selectedinterface for future visitors of the website.

In particular embodiments, the system is configured to test the two ormore test consent interfaces against one another by: (1) presenting afirst test interface of the two or more test consent interfaces to afirst portion of visitors to a website; (2) collecting first consentdata from the first portion of visitors based on the first testinterface; (3) presenting a second test interface of the two or moretest consent interfaces to a second portion of visitors to the website;(4) collecting second consent data from the second portion of visitorsbased on the second test interface; (5) analyzing and comparing thefirst consent data and second consent data to determine which of thefirst and second test interface results in a higher incidence of desiredconsent; and (6) selecting between the first and second test interfacebased on the analysis.

In particular embodiments, the system is configured to enable a user toselect a different template for each particular test interface. In anyembodiment described herein, the system is configured to automaticallyselect from a plurality of available templates when performing testing.In still any embodiment described herein, the system is configured toselect one or more interfaces for testing based on similar analysisperformed for one or more other websites.

In still any embodiment described herein, the system is configured touse one or more additional performance metrics when testing particularcookie consent interfaces (e.g., against one another). The one or moreadditional performance metrics may include, for example: (1) opt-inpercentage (e.g., a percentage of users that click the ‘accept all’button on a cookie consent test banner; (2) average time-to-interaction(e.g., an average time that users wait before interacting with aparticular test banner); (3) average time-to-site (e.g., an average timethat it takes a user to proceed to normal navigation across an entitysite after interacting with the cookie consent test banner; (4) dismisspercentage (e.g., a percentage of users that dismiss the cookie consentbanner using the close button, by scrolling, or by clicking ongrayed-out website); (5) functional cookies only percentage (e.g., apercentage of users that opt out of any cookies other than strictlynecessary cookies); (6) performance opt-out percentage; (7) targetingopt-out percentage; (8) social opt-out percentage; (9) etc.

Various embodiments of a consent conversion optimization system aredescribed more fully below.

In particular embodiments, an automated process blocking system isconfigured to substantially automatically block one or more processes(e.g., one or more data processing processes) based on received userconsent data. For example, as may be understood in light of thisdisclosure, a particular data subject may provide consent for an entityto process particular data associated with the data subject for one ormore particular purposes. In any embodiment of the system describedherein, the system may be configured to: (1) receive an indication thatone or more entity systems are processing one or more pieces of personaldata associated with a particular data subject; (2) in response toreceiving the indication, identifying at least one process for which theone or more pieces of personal data are being processed; (3) determine,using a consent receipt management system, whether the data subject hasprovided valid consent for the processing of the one or more pieces ofpersonal data for the at least one process; (4) at least partially inresponse to determining that the data subject has not provided validconsent for the processing of the one or more pieces of personal datafor the at least one process, automatically blocking the processing.

In particular embodiments, a consent receipt management system isconfigured to provide a centralized repository of consent receiptpreferences for a plurality of data subjects. In various embodiments,the system is configured to provide an interface to the plurality ofdata subjects for modifying consent preferences and capture consentpreference changes. The system may provide the ability to track theconsent status of pending and confirmed consents. In other embodiments,the system may provide a centralized repository of consent receipts thata third-party system may reference when taking one or more actionsrelated to a processing activity. For example, a particular entity mayprovide a newsletter that one or more data subjects have consented toreceiving. Each of the one or more data subjects may have differentpreferences related to how frequently they would like to receive thenewsletter, etc. In particular embodiments, the consent receiptmanagement system may receive a request form a third-party system totransmit the newsletter to the plurality of data subjects. The systemmay then cross-reference an updated consent database to determine whichof the data subjects have a current consent to receive the newsletter,and whether transmitting the newsletter would conflict with any of thosedata subjects' particular frequency preferences. The system may then beconfigured to transmit the newsletter to the appropriate identified datasubjects.

In various embodiments, the system may be configured to: (1) determinewhether there is a legal basis for processing of particular data priorto processing the data; (2) in response to determining that there is alegal basis, allowing the processing and generating a record for theprocessing that includes one or more pieces of evidence demonstratingthe legal basis (e.g., the user has consented, the processing isstrictly necessary, etc.); and (3) in response to determining that thereis no legal basis, blocking the processing from occurring. In particularembodiments, the system may be embodied as a processing permissionengine, which may, for example, interface with a consent receiptmanagement system. The system may, for example, be configured to accessthe consent receipt management system to determine whether an entity isable to process particular data for particular data subjects (e.g., forone or more particular purposes). In particular embodiments, one or moreentity computer system may be configured to interface with one or morethird party central consent data repositories prior to processing data(e.g., to determine whether the entity has consent or some other legalbasis for processing the data).

In particular other embodiments, the system is configured to perform oneor more risk analyses related to the processing in addition toidentifying whether the entity has consent or some other legal basis.The system may analyze the risk of the processing based on, for example:(1) a purpose of the processing; (2) a type of data being processed;and/or (3) any other suitable factor. In particular embodiments, thesystem is configured to determine whether to continue with theprocessing based on a combination of identifying a legal basis for theprocessing and the risk analysis. For example, the system may determinethat there is a legal basis to process the data, but that the processingis particularly risky. In this example, the system may determine toblock the processing of the data despite the legal basis because of thedetermined risk level. The risk analysis may be further based on, forexample, a risk tolerance of the entity/organization, or any othersuitable factor.

Various embodiments of an automated process blocking system aredescribed more fully below.

Exemplary Technical Platforms

As will be appreciated by one skilled in the relevant field, the presentinvention may be, for example, embodied as a computer system, a method,or a computer program product. Accordingly, various embodiments may takethe form of an entirely hardware embodiment, an entirely softwareembodiment, or an embodiment combining software and hardware aspects.Furthermore, particular embodiments may take the form of a computerprogram product stored on a computer-readable storage medium havingcomputer-readable instructions (e.g., software) embodied in the storagemedium. Various embodiments may take the form of web-implementedcomputer software. Any suitable computer-readable storage medium may beutilized including, for example, hard disks, compact disks, DVDs,optical storage devices, and/or magnetic storage devices.

Various embodiments are described below with reference to block diagramsand flowchart illustrations of methods, apparatuses (e.g., systems), andcomputer program products. It should be understood that each block ofthe block diagrams and flowchart illustrations, and combinations ofblocks in the block diagrams and flowchart illustrations, respectively,can be implemented by a computer executing computer programinstructions. These computer program instructions may be loaded onto ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions which execute on the computer or other programmabledata processing apparatus to create means for implementing the functionsspecified in the flowchart block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner such that the instructions stored in the computer-readable memoryproduce an article of manufacture that is configured for implementingthe function specified in the flowchart block or blocks. The computerprogram instructions may also be loaded onto a computer or otherprogrammable data processing apparatus to cause a series of operationalsteps to be performed on the computer or other programmable apparatus toproduce a computer implemented process such that the instructions thatexecute on the computer or other programmable apparatus provide stepsfor implementing the functions specified in the flowchart block orblocks.

Accordingly, blocks of the block diagrams and flowchart illustrationssupport combinations of mechanisms for performing the specifiedfunctions, combinations of steps for performing the specified functions,and program instructions for performing the specified functions. Itshould also be understood that each block of the block diagrams andflowchart illustrations, and combinations of blocks in the blockdiagrams and flowchart illustrations, can be implemented by specialpurpose hardware-based computer systems that perform the specifiedfunctions or steps, or combinations of special purpose hardware andother hardware executing appropriate computer instructions.

Example System Architecture

FIG. 1 is a block diagram of a Data Model Generation and PopulationSystem 100 according to a particular embodiment. In various embodiments,the Data Model Generation and Population System 100 is part of a privacycompliance system (also referred to as a privacy management system), orother system, which may, for example, be associated with a particularorganization and be configured to aid in compliance with one or morelegal or industry regulations related to the collection and storage ofpersonal data. In some embodiments, the Data Model Generation andPopulation System 100 is configured to: (1) generate a data model basedon one or more identified data assets, where the data model includes adata inventory associated with each of the one or more identified dataassets; (2) identify populated and unpopulated aspects of each datainventory; and (3) populate the unpopulated aspects of each datainventory using one or more techniques such as intelligent identityscanning, questionnaire response mapping, APIs, etc.

As may be understood from FIG. 1, the Data Model Generation andPopulation System 100 includes one or more computer networks 115, a DataModel Generation Server 110, a Data Model Population Server 120, anIntelligent Identity Scanning Server 130, One or More Databases 140 orother data structures, one or more remote computing devices 150 (e.g., adesktop computer, laptop computer, tablet computer, smartphone, etc.),and One or More Third Party Servers 160. In particular embodiments, theone or more computer networks 115 facilitate communication between theData Model Generation Server 110, Data Model Population Server 120,Intelligent Identity Scanning Server 130, One or More Databases 140, oneor more remote computing devices 150 (e.g., a desktop computer, laptopcomputer, tablet computer, smartphone, etc.), and One or More ThirdParty Servers 160. Although in the embodiment shown in FIG. 1, the DataModel Generation Server 110, Data Model Population Server 120,Intelligent Identity Scanning Server 130, One or More Databases 140, oneor more remote computing devices 150 (e.g., a desktop computer, laptopcomputer, tablet computer, smartphone, etc.), and One or More ThirdParty Servers 160 are shown as separate servers, it should be understoodthat in any embodiment described herein, one or more of these serversand/or computing devices may comprise a single server, a plurality ofservers, one or more cloud-based servers, or any other suitableconfiguration.

The one or more computer networks 115 may include any of a variety oftypes of wired or wireless computer networks such as the Internet, aprivate intranet, a public switch telephone network (PSTN), or any othertype of network. The communication link between The Intelligent IdentityScanning Server 130 and the One or More Third Party Servers 160 may be,for example, implemented via a Local Area Network (LAN) or via theInternet. In any embodiment described herein, the One or More Databases140 may be stored either fully or partially on any suitable server orcombination of servers described herein.

FIG. 2 illustrates a diagrammatic representation of a computer 200 thatcan be used within the Data Model Generation and Population System 100,for example, as a client computer (e.g., one or more remote computingdevices 130 shown in FIG. 1), or as a server computer (e.g., Data ModelGeneration Server 110 shown in FIG. 1). In particular embodiments, thecomputer 200 may be suitable for use as a computer within the context ofthe Data Model Generation and Population System 100 that is configuredto generate a data model and map one or more relationships between oneor more pieces of data that make up the model.

In particular embodiments, the computer 200 may be connected (e.g.,networked) to other computers in a LAN, an intranet, an extranet, and/orthe Internet. As noted above, the computer 200 may operate in thecapacity of a server or a client computer in a client-server networkenvironment, or as a peer computer in a peer-to-peer (or distributed)network environment. The Computer 200 may be a personal computer (PC), atablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), acellular telephone, a web appliance, a server, a network router, aswitch or bridge, or any other computer capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that computer. Further, while only a single computer is illustrated,the term “computer” shall also be taken to include any collection ofcomputers that individually or jointly execute a set (or multiple sets)of instructions to perform any one or more of the methodologiesdiscussed herein.

An exemplary computer 200 includes a processing device 202, a mainmemory 204 (e.g., read-only memory (ROM), flash memory, dynamic randomaccess memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM(RDRAM), etc.), static memory 206 (e.g., flash memory, static randomaccess memory (SRAM), etc.), and a data storage device 218, whichcommunicate with each other via a bus 232.

The processing device 202 represents one or more general-purposeprocessing devices such as a microprocessor, a central processing unit,or the like. More particularly, the processing device 202 may be acomplex instruction set computing (CISC) microprocessor, reducedinstruction set computing (RISC) microprocessor, very long instructionword (VLIW) microprocessor, or processor implementing other instructionsets, or processors implementing a combination of instruction sets. Theprocessing device 202 may also be one or more special-purpose processingdevices such as an application specific integrated circuit (ASIC), afield programmable gate array (FPGA), a digital signal processor (DSP),network processor, or the like. The processing device 202 may beconfigured to execute processing logic 226 for performing variousoperations and steps discussed herein.

The computer 120 may further include a network interface device 208. Thecomputer 200 also may include a video display unit 210 (e.g., a liquidcrystal display (LCD) or a cathode ray tube (CRT)), an alphanumericinput device 212 (e.g., a keyboard), a cursor control device 214 (e.g.,a mouse), and a signal generation device 216 (e.g., a speaker).

The data storage device 218 may include a non-transitorycomputer-accessible storage medium 230 (also known as a non-transitorycomputer-readable storage medium or a non-transitory computer-readablemedium) on which is stored one or more sets of instructions (e.g.,software instructions 222) embodying any one or more of themethodologies or functions described herein. The software instructions222 may also reside, completely or at least partially, within mainmemory 204 and/or within processing device 202 during execution thereofby computer 200—main memory 204 and processing device 202 alsoconstituting computer-accessible storage media. The softwareinstructions 222 may further be transmitted or received over a network115 via network interface device 208.

While the computer-accessible storage medium 230 is shown in anexemplary embodiment to be a single medium, the term“computer-accessible storage medium” should be understood to include asingle medium or multiple media (e.g., a centralized or distributeddatabase, and/or associated caches and servers) that store the one ormore sets of instructions. The term “computer-accessible storage medium”should also be understood to include any medium that is capable ofstoring, encoding or carrying a set of instructions for execution by thecomputer and that cause the computer to perform any one or more of themethodologies of the present invention. The term “computer-accessiblestorage medium” should accordingly be understood to include, but not belimited to, solid-state memories, optical and magnetic media, etc.

Exemplary System Platform

Various embodiments of a Data Model Generation and Population System 100may be implemented in the context of any suitable system (e.g., aprivacy compliance system). For example, the Data Model Generation andPopulation System 100 may be implemented to analyze a particular companyor other organization's data assets to generate a data model for one ormore processing activities, privacy campaigns, etc. undertaken by theorganization. In particular embodiments, the system may implement one ormore modules in order to at least partially ensure compliance with oneor more regulations (e.g., legal requirements) related to the collectionand/or storage of personal data. Various aspects of the system'sfunctionality may be executed by certain system modules, including aData Model Generation Module 300, Data Model Population Module 1100,Data Population Questionnaire Generation Module 1200, IntelligentIdentity Scanning Module 2600, and Data Subject Access RequestFulfillment Module 2900. These modules are discussed in greater detailbelow.

Although these modules are presented as a series of steps, it should beunderstood in light of this disclosure that various embodiments of theData Model Generation Module 300, Data Model Population Module 1100,Data Population Questionnaire Generation Module 1200, IntelligentIdentity Scanning Module 2600, and Data Subject Access RequestFulfillment Module 2900 described herein may perform the steps describedbelow in an order other than in which they are presented. In still anyembodiment described herein, the Data Model Generation Module 300, DataModel Population Module 1100, Data Population Questionnaire GenerationModule 1200, Intelligent Identity Scanning Module 2600, and Data SubjectAccess Request Fulfillment Module 2900 may omit certain steps describedbelow. In any embodiment described herein, the Data Model GenerationModule 300, Data Model Population Module 1100, Data PopulationQuestionnaire Generation Module 1200, Intelligent Identity ScanningModule 2600, and Data Subject Access Request Fulfillment Module 2900 mayperform steps in addition to those described (e.g., such as one or moresteps described with respect to one or more other modules, etc.).

Data Model Generation Module

In particular embodiments, a Data Model Generation Module 300 isconfigured to: (1) generate a data model (e.g., a data inventory) forone or more data assets utilized by a particular organization; (2)generate a respective data inventory for each of the one or more dataassets; and (3) map one or more relationships between one or moreaspects of the data inventory, the one or more data assets, etc. withinthe data model. In particular embodiments, a data asset (e.g., datasystem, software application, etc.) may include, for example, any entitythat collects, processes, contains, and/or transfers data (e.g., such asa software application, “internet of things” computerized device,database, website, data-center, server, etc.). For example, a first dataasset may include any software or device (e.g., server or servers)utilized by a particular entity for such data collection, processing,transfer, storage, etc.

In particular embodiments, a particular data asset, or collection ofdata assets, may be utilized as part of a particular data processingactivity (e.g., direct deposit generation for payroll purposes). Invarious embodiments, a data model generation system may, on behalf of aparticular organization (e.g., entity), generate a data model thatencompasses a plurality of processing activities. In any embodimentdescribed herein, the system may be configured to generate a discretedata model for each of a plurality of processing activities undertakenby an organization.

Turning to FIG. 3, in particular embodiments, when executing the DataModel Generation Module 300, the system begins, at Step 310, bygenerating a data model for one or more data assets and digitallystoring the data model in computer memory. The system may, for example,store the data model in the One or More Databases 140 described above(or any other suitable data structure). In various embodiments,generating the data model comprises generating a data structure thatcomprises information regarding one or more data assets, attributes andother elements that make up the data model. As may be understood inlight of this disclosure, the one or more data assets may include anydata assets that may be related to one another. In particularembodiments, the one or more data assets may be related by virtue ofbeing associated with a particular entity (e.g., organization). Forexample, the one or more data assets may include one or more computerservers owned, operated, or utilized by the entity that at leasttemporarily store data sent, received, or otherwise processed by theparticular entity.

In still any embodiment described herein, the one or more data assetsmay comprise one or more third party assets which may, for example,send, receive and/or process personal data on behalf of the particularentity. These one or more data assets may include, for example, one ormore software applications (e.g., such as Expensify to collect expenseinformation, QuickBooks to maintain and store salary information, etc.).

Continuing to step 320, the system is configured to identify a firstdata asset of the one or more data assets. In particular embodiments,the first data asset may include, for example, any entity (e.g., system)that collects, processes, contains, and/or transfers data (e.g., such asa software application, “internet of things” computerized device,database, website, data-center, server, etc.). For example, the firstdata asset may include any software or device utilized by a particularorganization for such data collection, processing, transfer, etc. Invarious embodiments, the first data asset may be associated with aparticular processing activity (e.g., the first data asset may make upat least a part of a data flow that relates to the collection, storage,transfer, access, use, etc. of a particular piece of data (e.g.,personal data)). Information regarding the first data asset may clarify,for example, one or more relationships between and/or among one or moreother data assets within a particular organization. In a particularexample, the first data asset may include a software applicationprovided by a third party (e.g., a third party vendor) with which theparticular entity interfaces for the purpose of collecting, storing, orotherwise processing personal data (e.g., personal data regardingcustomers, employees, potential customers, etc.).

In particular embodiments, the first data asset is a storage asset thatmay, for example: (1) receive one or more pieces of personal data formone or more collection assets; (2) transfer one or more pieces ofpersonal data to one or more transfer assets; and/or (3) provide accessto one or more pieces of personal data to one or more authorizedindividuals (e.g., one or more employees, managers, or other authorizedindividuals within a particular entity or organization). In a particularembodiment, the first data asset is a primary data asset associated witha particular processing activity around which the system is configuredto build a data model associated with the particular processingactivity.

In particular embodiments, the system is configured to identify thefirst data asset by scanning a plurality of computer systems associatedwith a particular entity (e.g., owned, operated, utilized, etc. by theparticular entity). In various embodiments, the system is configured toidentify the first data asset from a plurality of data assets identifiedin response to completion, by one or more users, of one or morequestionnaires.

Advancing to Step 330, the system generates a first data inventory ofthe first data asset. The data inventory may comprise, for example, oneor more inventory attributes associated with the first data asset suchas, for example: (1) one or more processing activities associated withthe first data asset; (2) transfer data associated with the first dataasset (e.g., how and where the data is being transferred to and/orfrom); (3) personal data associated with the first data asset (e.g.,what type of personal data is collected and/or stored by the first dataasset; how, and from where, the data is collected, etc.); (4) storagedata associated with the personal data (e.g., whether the data is beingstored, protected and deleted); and (5) any other suitable attributerelated to the collection, use, and transfer of personal data. In anyembodiment described herein, the one or more inventory attributes maycomprise one or more other pieces of information such as, for example:(1) the type of data being stored by the first data asset; (2) an amountof data stored by the first data asset; (3) whether the data isencrypted; (4) a location of the stored data (e.g., a physical locationof one or more computer servers on which the data is stored); etc. Inparticular any embodiment described herein, the one or more inventoryattributes may comprise one or more pieces of information technologydata related to the first data asset (e.g., such as one or more piecesof network and/or infrastructure information, IP address, MAC address,etc.).

In various embodiments, the system may generate the data inventory basedat least in part on the type of first data asset. For example,particular types of data assets may have particular default inventoryattributes. In such embodiments, the system is configured to generatethe data inventory for the first data asset, which may, for example,include one or more placeholder fields to be populated by the system ata later time. In this way, the system may, for example, identifyparticular inventory attributes for a particular data asset for whichinformation and/or population of data is required as the system buildsthe data model.

As may be understood in light of this disclosure, the system may, whengenerating the data inventory for the first data asset, generate one ormore placeholder fields that may include, for example: (1) theorganization (e.g., entity) that owns and/or uses the first data asset(a primary data asset, which is shown in the center of the data model inFIG. 4); (2) one or more departments within the organization that areresponsible for the first data asset; (3) one or more softwareapplications that collect data (e.g., personal data) for storage inand/or use by the first data asset (e.g., or one or more other suitablecollection assets from which the personal data that is collected,processed, stored, etc. by the first data asset is sourced); (4) one ormore particular data subjects (or categories of data subjects) thatinformation is collected from for use by the first data asset; (5) oneor more particular types of data that are collected by each of theparticular applications for storage in and/or use by the first dataasset; (6) one or more individuals (e.g., particular individuals ortypes of individuals) that are permitted to access and/or use the datastored in, or used by, the first data asset; (7) which particular typesof data each of those individuals are allowed to access and use; and (8)one or more data assets (destination assets) that the data istransferred to from the first data asset, and which particular data istransferred to each of those data assets.

As may be understood in light of this disclosure, the system may beconfigured to generate the one or more placeholder fields based at leastin part on, for example: (1) the type of the first data asset; (2) oneor more third party vendors utilized by the particular organization; (3)a number of collection or storage assets typically associated with thetype of the first data asset; and/or (4) any other suitable factorrelated to the first data asset, its one or more inventory attributes,etc. In any embodiment described herein, the system may substantiallyautomatically generate the one or more placeholders based at least inpart on a hierarchy and/or organization of the entity for which the datamodel is being built. For example, a particular entity may have amarketing division, legal department, human resources department,engineering division, or other suitable combination of departments thatmake up an overall organization. Other particular entities may havefurther subdivisions within the organization. When generating the datainventory for the first data asset, the system may identify that thefirst data asset will have both an associated organization andsubdivision within the organization to which it is assigned. In thisexample, the system may be configured to store an indication in computermemory that the first data asset is associated with an organization anda department within the organization.

Next, at Step 340, the system modifies the data model to include thefirst data inventory and electronically links the first data inventoryto the first data asset within the data model. In various embodiments,modifying the data model may include configuring the data model to storethe data inventory in computer memory, and to digitally associate thedata inventory with the first data asset in memory.

FIGS. 4 and 5 show a data model according to a particular embodiment. Asshown in these figures, the data model may store the followinginformation for the first data asset: (1) the organization that ownsand/or uses the first data asset; (2) one or more departments within theorganization that are responsible for the first data asset; (3) one ormore applications that collect data (e.g., personal data) for storage inand/or use by the first data asset; (4) one or more particular datasubjects that information is collected from for use by the first dataasset; (5) one or more collection assets from which the first assetreceives data (e.g., personal data); (6) one or more particular types ofdata that are collected by each of the particular applications (e.g.,collection assets) for storage in and/or use by the first data asset;(7) one or more individuals (e.g., particular individuals, types ofindividuals, or other parties) that are permitted to access and/or usethe data stored in or used by the first data asset; (8) which particulartypes of data each of those individuals are allowed to access and use;and (9) one or more data assets (destination assets) the data istransferred to for other use, and which particular data is transferredto each of those data assets. As shown in FIGS. 6 and 7, the system mayalso optionally store information regarding, for example, which businessprocesses and processing activities utilize the first data asset.

As noted above, in particular embodiments, the data model stores thisinformation for each of a plurality of different data assets and mayinclude one or more links between, for example, a portion of the modelthat provides information for a first particular data asset and a secondportion of the model that provides information for a second particulardata asset.

Advancing to Step 350, the system next identifies a second data assetfrom the one or more data assets. In various embodiments, the seconddata asset may include one of the one or more inventory attributesassociated with the first data asset (e.g., the second data asset mayinclude a collection asset associated with the first data asset, adestination asset or transfer asset associated with the first dataasset, etc.). In various embodiments, as may be understood in light ofthe exemplary data models described below, a second data asset may be aprimary data asset for a second processing activity, while the firstdata asset is the primary data asset for a first processing activity. Insuch embodiments, the second data asset may be a destination asset forthe first data asset as part of the first processing activity. Thesecond data asset may then be associated with one or more seconddestination assets to which the second data asset transfers data. Inthis way, particular data assets that make up the data model may defineone or more connections that the data model is configured to map andstore in memory.

Returning to Step 360, the system is configured to identify one or moreattributes associated with the second data asset, modify the data modelto include the one or more attributes, and map the one or moreattributes of the second data asset within the data model. The systemmay, for example, generate a second data inventory for the second dataasset that comprises any suitable attribute described with respect tothe first data asset above. The system may then modify the data model toinclude the one or more attributes and store the modified data model inmemory. The system may further, in various embodiments, associate thefirst and second data assets in memory as part of the data model. Insuch embodiments, the system may be configured to electronically linkthe first data asset with the second data asset. In various embodiments,such association may indicate a relationship between the first andsecond data assets in the context of the overall data model (e.g.,because the first data asset may serve as a collection asset for thesecond data asset, etc.).

Next, at Step 370, the system may be further configured to generate avisual representation of the data model. In particular embodiments, thevisual representation of the data model comprises a data map. The visualrepresentation may, for example, include the one or more data assets,one or more connections between the one or more data assets, the one ormore inventory attributes, etc.

In particular embodiments, generating the visual representation (e.g.,visual data map) of a particular data model (e.g., data inventory) mayinclude, for example, generating a visual representation that includes:(1) a visual indication of a first data asset (e.g., a storage asset), asecond data asset (e.g., a collection asset), and a third data asset(e.g., a transfer asset); (2) a visual indication of a flow of data(e.g., personal data) from the second data asset to the first data asset(e.g., from the collection asset to the storage asset); (3) a visualindication of a flow of data (e.g., personal data) from the first dataasset to the third data asset (e.g., from the storage asset to thetransfer asset); (4) one or more visual indications of a risk levelassociated with the transfer of personal data; and/or (5) any othersuitable information related to the one or more data assets, thetransfer of data between/among the one or more data assets, access todata stored or collected by the one or more data assets, etc.

In particular embodiments, the visual indication of a particular assetmay comprise a box, symbol, shape, or other suitable visual indicator.In particular embodiments, the visual indication may comprise one ormore labels (e.g., a name of each particular data asset, a type of theasset, etc.). In still any embodiment described herein, the visualindication of a flow of data may comprise one or more arrows. Inparticular embodiments, the visual representation of the data model maycomprise a data flow, flowchart, or other suitable visualrepresentation.

In various embodiments, the system is configured to display (e.g., to auser) the generated visual representation of the data model on asuitable display device.

Exemplary Data Models and Visual Representations of Data Models (e.g.,Data Maps)

FIGS. 4-10 depict exemplary data models according to various embodimentsof the system described herein. FIG. 4, for example, depicts anexemplary data model that does not include a particular processingactivity (e.g., that is not associated with a particular processingactivity). As may be understood from the data model shown in thisfigure, a particular data asset (e.g., a primary data asset) may beassociated with a particular company (e.g., organization), ororganization within a particular company, sub-organization of aparticular organization, etc. In still any embodiment described herein,the particular asset may be associated with one or more collectionassets (e.g., one or more data subjects from whom personal data iscollected for storage by the particular asset), one or more parties thathave access to data stored by the particular asset, one or more transferassets (e.g., one or more assets to which data stored by the particularasset may be transferred), etc.

As may be understood from FIG. 4, a particular data model for aparticular asset may include a plurality of data elements. Whengenerating the data model for the particular asset, a system may beconfigured to substantially automatically identify one or more types ofdata elements for inclusion in the data model, and automaticallygenerate a data model that includes those identified data elements(e.g., even if one or more of those data elements must remainunpopulated because the system may not initially have access to a valuefor the particular data element). In such cases, the system may beconfigured to store a placeholder for a particular data element untilthe system is able to populate the particular data element with accuratedata.

As may be further understood from FIG. 4, the data model shown in FIG. 4may represent a portion of an overall data model. For example, in theembodiment shown in this figure, the transfer asset depicted may serveas a storage asset for another portion of the data model. In suchembodiments, the transfer asset may be associated with a respective oneor more of the types of data elements described above. In this way, thesystem may generate a data model that may build upon itself to comprisea plurality of layers as the system adds one or more new data assets,attributes, etc.

As may be further understood from FIG. 4, a particular data model mayindicate one or more parties that have access to and/or use of theprimary asset (e.g., storage asset). In such embodiments, the system maybe configured to enable the one or more parties to access one or morepieces of data (e.g., personal data) stored by the storage asset.

As shown in FIG. 4, the data model may further comprise one or morecollection assets (e.g., one or more data assets or individuals fromwhich the storage asset receives data such as personal data). In theexemplary data model (e.g., visual data map) shown in this figure, thecollection assets comprise a data subject (e.g., an individual that mayprovide data to the system for storage in the storage asset) and acollection asset (e.g., which may transfer one or more pieces of datathat the collection asset has collected to the storage asset).

FIG. 5 depicts a portion of an exemplary data model that is populatedfor the primary data asset Gusto. Gusto is a software application that,in the example shown in FIG. 5, may serve as a human resources servicethat contains financial, expense, review, time and attendance,background, and salary information for one or more employees of aparticular organization (e.g., GeneriTech). In the example of FIG. 5,the primary asset (e.g., Gusto) may be utilized by the HR (e.g., HumanResources) department of the particular organization (e.g., GeneriTech).Furthermore, the primary asset, Gusto, may collect financial informationfrom one or more data subjects (e.g., employees of the particularorganization), receive expense information transferred from Expensify(e.g., expensing software), and receive time and attendance datatransferred from Kronos (e.g., timekeeping software). In the exampleshown in FIG. 5, access to the information collected and/or stored byGusto may include, for example: (1) an ability to view and administersalary and background information by HR employees, and (2) an ability toview and administer employee review information by one or more servicemanagers. In the example shown in this figure, personal and other datacollected and stored by Gusto (e.g., salary information, etc.) may betransferred to a company banking system, to QuickBooks, and/or to an HRfile cabinet.

As may be understood from the example shown in FIG. 5, the system may beconfigured to generate a data model based around Gusto that illustratesa flow of personal data utilized by Gusto. The data model in thisexample illustrates, for example, a source of personal data collected,stored and/or processed by Gusto, a destination of such data, anindication of who has access to such data within Gusto, and anorganization and department responsible for the information collected byGusto. In particular embodiments, the data model and accompanying visualrepresentation (e.g., data map) generated by the system as described inany embodiment herein may be utilized in the context of compliance withone or more record keeping requirements related to the collection,storage, and processing of personal data.

FIGS. 6 and 7 depict an exemplary data model and related example that issimilar, in some respects, to the data model and example of FIGS. 4 and5. In the example shown in FIGS. 6 and 7, the exemplary data model andrelated example include a specific business process and processingactivity that is associated with the primary asset (Gusto). In thisexample, the business process is compensation and the specificprocessing activity is direct deposit generation in Gusto. As may beunderstood from this figure, the collection and transfer of data relatedto the storage asset of Gusto is based on a need to generate directdeposits through Gusto in order to compensate employees. Gusto generatesthe information needed to conduct a direct deposit (e.g., financial andsalary information) and then transmits this information to: (1) acompany bank system for execution of the direct deposit; (2) Quickbooksfor use in documenting the direct deposit payment; and (3) HR Filecabinet for use in documenting the salary info and other financialinformation.

As may be understood in light of this disclosure, when generating such adata model, particular pieces of data (e.g., data attributes, dataelements) may not be readily available to the system. In suchembodiment, the system is configured to identify a particular type ofdata, create a placeholder for such data in memory, and seek out (e.g.,scan for and populate) an appropriate piece of data to further populatethe data model. For example, in particular embodiments, the system mayidentify Gusto as a primary asset and recognize that Gusto storesexpense information. The system may then be configured to identify asource of the expense information (e.g., Expensify).

FIG. 8 depicts an exemplary screen display 800 that illustrates a visualrepresentation (e.g., visual data map) of a data model (e.g., a datainventory). In the example shown in FIG. 8, the data map provides avisual indication of a flow of data collected from particular datasubjects (e.g., employees 801). As may be understood from this figure,the data map illustrates that three separate data assets receive data(e.g., which may include personal data) directly from the employees 801.In this example, these three data assets include Kronos 803 (e.g., ahuman resources software application), Workday 805 (e.g., a humanresources software application), and ADP 807 (e.g., a human resourcessoftware application and payment processor). As shown in FIG. 8, thetransfer of data from the employees 801 to these assets is indicated byrespective arrows.

As further illustrated in FIG. 8, the data map indicates a transfer ofdata from Workday 805 to ADP 807 as well as to a Recovery Datacenter 809and a London HR File Center 811. As may be understood in light of thisdisclosure, the Recovery Datacenter 809 and London HR File Center 811may comprise additional data assets in the context of the data modelillustrated by the data map shown in FIG. 8. The Recover Datacenter 809may include, for example, one or more computer servers (e.g., backupservers). The London HR File Center 811 may include, for example, one ormore databases (e.g., such as the One or More Databases 140 shown inFIG. 1). AS shown in FIG. 8, each particular data asset depicted in thedata map may be shown along with a visual indication of the type of dataasset. For example, Kronos 803, Workday 805, and ADP 807 are depictedadjacent a first icon type (e.g., a computer monitor), while RecoverDatacenter 809 and London HR File Center 811 are depicted adjacent asecond and third icon type respectively (e.g., a server cluster and afile folder). In this way, the system may be configured to visuallyindicate, via the data model, particular information related to the datamodel in a relatively minimal manner.

FIG. 9 depicts an exemplary screen display 900 that illustrates a datamap of a plurality of assets 905 in tabular form (e.g., table form). Asmay be understood from this figure, a table that includes one or moreinventory attributes of each particular asset 905 in the table mayindicate, for example: (1) a managing organization 910 of eachrespective asset 905; (2) a hosting location 915 of each respectiveasset 905 (e.g., a physical storage location of each asset 905); (3) atype 920 of each respective asset 905, if known (e.g., a database,software application, server, etc.); (4) a processing activity 925associated with each respective asset 905; and/or (5) a status 930 ofeach particular data asset 905. In various embodiments, the status 930of each particular asset 905 may indicate a status of the asset 905 inthe discovery process. This may include, for example: (1) a “new” statusfor a particular asset that has recently been discovered as an assetthat processes, stores, or collects personal data on behalf of anorganization (e.g., discovered via one or more suitable techniquesdescribed herein); (2) an “in discovery” status for a particular assetfor which the system is populating or seeking to populate one or moreinventory attributes, etc.

FIG. 10 depicts an exemplary data map 1000 that includes an asset map ofa plurality of data assets 1005A-F, which may, for example, be utilizedby a particular entity in the collection, storage, and/or processing ofpersonal data. As may be understood in light of this disclosure, theplurality of data assets 1005A-F may have been discovered using anysuitable technique described herein (e.g., one or more intelligentidentity scanning techniques, one or more questionnaires, one or moreapplication programming interfaces, etc.). In various embodiments, adata inventory for each of the plurality of data assets 1005A-F maydefine, for each of the plurality of data assets 1005A-F a respectiveinventory attribute related to a storage location of the data asset.

As may be understood from this figure, the system may be configured togenerate a map that indicates a location of the plurality of data assets1005A-F for a particular entity. In the embodiment shown in this figure,locations that contain a data asset are indicated by circular indiciathat contain the number of assets present at that location. In theembodiment shown in this figure, the locations are broken down bycountry. In particular embodiments, the asset map may distinguishbetween internal assets (e.g., first party servers, etc.) andexternal/third party assets (e.g., third party owned servers or softwareapplications that the entity utilizes for data storage, transfer, etc.).

In some embodiments, the system is configured to indicate, via thevisual representation, whether one or more assets have an unknownlocation (e.g., because the data model described above may be incompletewith regard to the location). In such embodiments, the system may beconfigured to: (1) identify the asset with the unknown location; (2) useone or more data modeling techniques described herein to determine thelocation (e.g., such as pinging the asset, generating one or morequestionnaires for completion by a suitable individual, etc.); and (3)update a data model associated with the asset to include the location.

Data Model Population Module

In particular embodiments, a Data Model Population Module 1100 isconfigured to: (1) determine one or more unpopulated inventoryattributes in a data model; (2) determine one or more attribute valuesfor the one or more unpopulated inventory attributes; and (3) modify thedata model to include the one or more attribute values.

Turning to FIG. 11, in particular embodiments, when executing the DataModel Population Module 1100, the system begins, at Step 1110, byanalyzing one or more data inventories for each of the one or more dataassets in the data model. The system may, for example, identify one ormore particular data elements (e.g., inventory attributes) that make upthe one or more data inventories. The system may, in variousembodiments, scan one or more data structures associated with the datamodel to identify the one or more data inventories. In variousembodiments, the system is configured to build an inventory of existing(e.g., known) data assets and identify inventory attributes for each ofthe known data assets.

Continuing to Step 1120, the system is configured to determine, for eachof the one or more data inventories, one or more populated inventoryattributes and one or more unpopulated inventory attributes (e.g.,and/or one or more unpopulated data assets within the data model). As aparticular example related to an unpopulated data asset, when generatingand populating a data model, the system may determine that, for aparticular asset, there is a destination asset. In various embodiments,the destination asset may be known (e.g., and already stored by thesystem as part of the data model). In any embodiment described herein,the destination asset may be unknown (e.g., a data element thatcomprises the destination asset may comprise a placeholder or otherindication in memory for the system to populate the unpopulatedinventory attribute (e.g., data element).

As another particular example, a particular storage asset may beassociated with a plurality of inventory assets (e.g., stored in a datainventory associated with the storage asset). In this example, theplurality of inventory assets may include an unpopulated inventoryattribute related to a type of personal data stored in the storageasset. The system may, for example, determine that the type of personaldata is an unpopulated inventory asset for the particular storage asset.

Returning to Step 1130, the system is configured to determine, for eachof the one or more unpopulated inventory attributes, one or moreattribute values. In particular embodiments, the system may determinethe one or more attribute values using any suitable technique (e.g., anysuitable technique for populating the data model). In particularembodiments, the one or more techniques for populating the data modelmay include, for example: (1) obtaining data for the data model by usingone or more questionnaires associated with a particular privacycampaign, processing activity, etc.; (2) using one or more intelligentidentity scanning techniques discussed herein to identify personal datastored by the system and then map such data to a suitable data model;(3) using one or more application programming interfaces (API) to obtaindata for the data model from another software application; and/or (4)using any other suitable technique. Exemplary techniques for determiningthe one or more attribute values are described more fully below. In anyembodiment described herein, the system may be configured to use suchtechniques or other suitable techniques to populate one or moreunpopulated data assets within the data model.

Next, at Step 1140, the system modifies the data model to include theone or more attribute values for each of the one or more unpopulatedinventory attributes. The system may, for example, store the one or moreattributes values in computer memory, associate the one or moreattribute values with the one or more unpopulated inventory attributes,etc. In still any embodiment described herein, the system may modify thedata model to include the one or more data assets identified as fillingone or more vacancies left within the data model by the unpopulated oneor more data assets.

Continuing to Step 1150, the system is configured to store the modifieddata model in memory. In various embodiments, the system is configuredto store the modified data model in the One or More Databases 140, or inany other suitable location. In particular embodiments, the system isconfigured to store the data model for later use by the system in theprocessing of one or more data subject access requests. In anyembodiment described herein, the system is configured to store the datamodel for use in one or more privacy impact assessments performed by thesystem.

Data Model Population Questionnaire Generation Module

In particular embodiments, a Data Population Questionnaire GenerationModule 1200 is configured to generate a questionnaire (e.g., one or morequestionnaires) comprising one or more questions associated with one ormore particular unpopulated data attributes, and populate theunpopulated data attributes based at least in part on one or moreresponses to the questionnaire. In any embodiment described herein, thesystem may be configured to populate the unpopulated data attributesbased on one or more responses to existing questionnaires.

In various embodiments, the one or more questionnaires may comprise oneor more processing activity questionnaires (e.g., privacy impactassessments, data privacy impact assessments, etc.) configured to elicitone or more pieces of data related to one or more undertakings by anorganization related to the collection, storage, and/or processing ofpersonal data (e.g., processing activities). In particular embodiments,the system is configured to generate the questionnaire (e.g., aquestionnaire template) based at least in part on one or more processingactivity attributes, data asset attributes (e.g., inventory attributes),or other suitable attributes discussed herein.

Turning to FIG. 12, in particular embodiments, when executing the DataPopulation Questionnaire Generation Module 1200, the system begins, atStep 1210, by identifying one or more unpopulated data attributes from adata model. The system may, for example, identify the one or moreunpopulated data attributes using any suitable technique describedabove. In particular embodiments, the one or more unpopulated dataattributes may relate to, for example, one or more processing activityor asset attributes such as: (1) one or more processing activitiesassociated with a particular data asset; (2) transfer data associatedwith the particular data asset (e.g., how and where the data storedand/or collected by the particular data asset is being transferred toand/or from); (3) personal data associated with the particular dataassets asset (e.g., what type of personal data is collected and/orstored by the particular data asset; how, and from where, the data iscollected, etc.); (4) storage data associated with the personal data(e.g., whether the data is being stored, protected and deleted); and (5)any other suitable attribute related to the collection, use, andtransfer of personal data by one or more data assets or via one or moreprocessing activities. In any embodiment described herein, the one ormore unpopulated inventory attributes may comprise one or more otherpieces of information such as, for example: (1) the type of data beingstored by the particular data asset; (2) an amount of data stored by theparticular data asset; (3) whether the data is encrypted by theparticular data asset; (4) a location of the stored data (e.g., aphysical location of one or more computer servers on which the data isstored by the particular data asset); etc.

Continuing to Step 1220, the system generates a questionnaire (e.g., aquestionnaire template) comprising one or more questions associated withone or more particular unpopulated data attributes. As may be understoodin light of the above, the one or more particulate unpopulated dataattributes may relate to, for example, a particular processing activityor a particular data asset (e.g., a particular data asset utilized aspart of a particular processing activity). In various embodiments, theone or more questionnaires comprise one or more questions associatedwith the unpopulated data attribute. For example, if the data modelincludes an unpopulated data attribute related to a location of a serveron which a particular asset stores personal data, the system maygenerate a questionnaire associated with a processing activity thatutilizes the asset (e.g., or a questionnaire associated with the asset).The system may generate the questionnaire to include one or morequestions regarding the location of the server.

Returning to Step 1230, the system maps one or more responses to the oneor more questions to the associated one or more particular unpopulateddata attributes. The system may, for example, when generating thequestionnaire, associate a particular question with a particularunpopulated data attribute in computer memory. In various embodiments,the questionnaire may comprise a plurality of question/answer pairings,where the answer in the question/answer pairings maps to a particularinventory attribute for a particular data asset or processing activity.

In this way, the system may, upon receiving a response to the particularquestion, substantially automatically populate the particularunpopulated data attribute. Accordingly, at Step 1240, the systemmodifies the data model to populate the one or more responses as one ormore data elements for the one or more particular unpopulated dataattributes. In particular embodiments, the system is configured tomodify the data model such that the one or more responses are stored inassociation with the particular data element (e.g., unpopulated dataattribute) to which the system mapped it at Step 1230. In variousembodiments, the system is configured to store the modified data modelin the One or More Databases 140, or in any other suitable location. Inparticular embodiments, the system is configured to store the data modelfor later use by the system in the processing of one or more datasubject access requests. In any embodiment described herein, the systemis configured to store the data model for use in one or more privacyimpact assessments performed by the system.

Continuing to optional Step 1250, the system may be configured to modifythe questionnaire based at least in part on the one or more responses.The system may, for example, substantially dynamically add and/or removeone or more questions to/from the questionnaire based at least in parton the one or more responses (e.g., one or more response received by auser completing the questionnaire). For example, the system may, inresponse to the user providing a particular inventory attribute or newasset, generates additional questions that relate to that particularinventory attribute or asset. The system may, as the system addsadditional questions, substantially automatically map one or moreresponses to one or more other inventory attributes or assets. Forexample, in response to the user indicating that personal data for aparticular asset is stored in a particular location, the system maysubstantially automatically generate one or more additional questionsrelated to, for example, an encryption level of the storage, who hasaccess to the storage location, etc.

In still any embodiment described herein, the system may modify the datamodel to include one or more additional assets, data attributes,inventory attributes, etc. in response to one or more questionnaireresponses. For example, the system may modify a data inventory for aparticular asset to include a storage encryption data element (whichspecifies whether the particular asset stores particular data in anencrypted format) in response to receiving such data from aquestionnaire. Modification of a questionnaire is discussed more fullybelow with respect to FIG. 13.

Data Model Population Via Questionnaire Process Flow

FIG. 13 depicts an exemplary process flow 1300 for populating a datamodel (e.g., modifying a data model to include a newly discovered dataasset, populating one or more inventory attributes for a particularprocessing activity or data asset, etc.). In particular, FIG. 13 depictsone or more exemplary data relationships between one or more particulardata attributes (e.g., processing activity attributes and/or assetattributes), a questionnaire template (e.g., a processing activitytemplate and/or a data asset template), a completed questionnaire (e.g.,a processing activity assessment and/or a data asset assessment), and adata inventory (e.g., a processing activity inventory and/or an assetinventory). As may be understood from this figure the system isconfigured to: (1) identify new data assets; (2) generate an assetinventory for identified new data assets; and (3) populate the generatedasset inventories. Systems and methods for populating the generatedinventories are described more fully below.

As may be understood from FIG. 13, a system may be configured to mapparticular processing activity attributes 1320A to each of: (1) aprocessing activity template 1330A; and (2) a processing activity datainventory 1310A. As may be understood in light of this disclosure, theprocessing activity template 1330A may comprise a plurality of questions(e.g., as part of a questionnaire), which may, for example, beconfigured to elicit discovery of one or more new data assets. Theplurality of questions may each correspond to one or more fields in theprocessing activity inventory 1310A, which may, for example, define oneor more inventory attributes of the processing activity.

In particular embodiments, the system is configured to provide aprocessing activity assessment 1340A to one or more individuals forcompletion. As may be understood from FIG. 13, the system is configuredto launch the processing activity assessment 1340A from the processingactivity inventory 1310A and further configured to create the processingactivity assessment 1340A from the processing activity template 1330.The processing activity assessment 1340A may comprise, for example, oneor more questions related to the processing activity. The system may, invarious embodiments, be configured to map one or more responses providedin the processing activity assessment 1340A to one or more correspondingfields in the processing activity inventory 1310A. The system may thenbe configured to modify the processing activity inventory 1310A toinclude the one or more responses and store the modified inventory incomputer memory. In various embodiments, the system may be configured toapprove a processing activity assessment 1340A (e.g., receive approvalof the assessment) prior to feeding the processing activity inventoryattribute values into one or more fields and/or cells of the inventory.

As may be further understood from FIG. 13, in response to creating a newasset record (e.g., which the system may create, for example, inresponse to a new asset discovery via the processing activity assessment1340A described immediately above, or in any other suitable manner), thesystem may generate an asset inventory 1310B (e.g., a data assetinventory) that defines a plurality of inventory attributes for the newasset (e.g., new data asset).

As may be understood from FIG. 13, a system may be configured to mapparticular asset attributes 1320B to each of: (1) an asset template1330BA; and (2) an asset inventory 1310A. As may be understood in lightof this disclosure, the asset template 1330B may comprise a plurality ofquestions (e.g., as part of a questionnaire), which may, for example, beconfigured to elicit discovery of one or more processing activitiesassociated with the asset and/or one or more inventory attributes of theasset. The plurality of questions may each correspond to one or morefields in the asset inventory 1310B, which may, for example, define oneor more inventory attributes of the asset.

In particular embodiments, the system is configured to provide an assetassessment 1340B to one or more individuals for completion. As may beunderstood from FIG. 13, the system is configured to launch the assetassessment 1340B from the asset inventory 1310B and further configuredto create the asset assessment 1340B from the asset template 1330B. Theasset assessment 1340B may comprise, for example, one or more questionsrelated to the data asset. The system may, in various embodiments, beconfigured to map one or more responses provided in the asset assessment1340B to one or more corresponding fields in the asset inventory 1310B.The system may then be configured to modify the asset inventory 1310B(e.g., and/or a related processing activity inventory 1310A) to includethe one or more responses and store the modified inventory in computermemory. In various embodiments, the system may be configured to approvean asset assessment 1340B (e.g., receive approval of the assessment)prior to feeding the asset inventory attribute values into one or morefields and/or cells of the inventory.

FIG. 13 further includes a detail view 1350 of a relationship betweenparticular data attributes 1320C with an exemplary data inventory 1310Cand a questionnaire template 1330C. As may be understood from thisdetail view 1350, a particular attribute name may map to a particularquestion title in a template 1330C as well as to a field name in anexemplary data inventory 1310C. In this way, the system may beconfigured to populate (e.g., automatically populate) a field name for aparticular inventory 1310C in response to a user providing a questiontitle as part of a questionnaire template 1330C. Similarly, a particularattribute description may map to a particular question description in atemplate 1330C as well as to a tooltip on a fieldname in an exemplarydata inventory 1310C. In this way, the system may be configured toprovide the tooltip for a particular inventory 1310C that includes thequestion description provided by a user as part of a questionnairetemplate 1330C.

As may be further understood from the detail view 1350 of FIG. 13, aparticular response type may map to a particular question type in atemplate 1330C as well as to a field type in an exemplary data inventory1310C. A particular question type may include, for example, amultiple-choice question (e.g., A, B, C, etc.), a freeform response, aninteger value, a drop-down selection, etc. A particular field type mayinclude, for example, a memo field type, a numeric field type, aninteger field type, a logical field type, or any other suitable fieldtype. A particular data attribute may require a response type of, forexample: (1) a name of an organization responsible for a data asset(e.g., a free form response); (2) a number of days that data is storedby the data asset (e.g., an integer value); and/or (3) any othersuitable response type.

In still any embodiment described herein, the system may be configuredto map a one or more attribute values to one or more answer choices in atemplate 1330C as well as to one or more lists and/or responses in adata inventory 1310C. The system may then be configured to populate afield in the data inventory 1310C with the one or more answer choicesprovided in a response to a question template 1330C with one or moreattribute values.

Exemplary Questionnaire Generation and Completion User Experience

FIGS. 14-25 depict exemplary screen displays that a user may encounterwhen generating a questionnaire (e.g., one or more questionnaires and/ortemplates) for populating one or more data elements (e.g., inventoryattributes) of a data model for a data asset and/or processing activity.FIG. 14, for example, depicts an exemplary asset-based questionnairetemplate builder 1400. As may be understood from FIG. 14, the templatebuilder may enable a user to generate an asset-based questionnairetemplate that includes one or more sections 1420 related to the asset(e.g., asset information, security, disposal, processing activities,etc.). As may be understood in light of this disclosure, the system maybe configured to substantially automatically generate an asset-basedquestionnaire template based at least in part on the one or moreunpopulated inventory attributes discussed above. The system may, forexample, be configured to generate a template that is configured topopulate the one or more unpopulated attributes (e.g., by elicitingresponses, via a questionnaire to one or more questions that are mappedto the attributes within the data inventory).

In various embodiments, the system is configured to enable a user tomodify a default template (e.g., or a system-created template) by, forexample, adding additional sections, adding one or more additionalquestions to a particular section, etc. In various embodiments, thesystem may provide one or more tools for modifying the template. Forexample, in the embodiment shown in FIG. 14, the system may provide auser with a draft and drop question template 1410, from which the usermay select a question type (e.g., textbox, multiple choice, etc.).

A template for an asset may include, for example: (1) one or morequestions requesting general information about the asset; (2) one ormore security-related questions about the asset; (3) one or morequestions regarding how the data asset disposes of data that it uses;and/or (4) one or more questions regarding processing activities thatinvolve the data asset. In various embodiments, each of these one ormore sections may comprise one or more specific questions that may mapto particular portions of a data model (e.g., a data map).

FIG. 15 depicts an exemplary screen display of a processing activityquestionnaire template builder 1500. The screen display shown in FIG. 15is similar to the template builder shown in FIG. 14 with respect to thedata asset-based template builder. As may be understood from FIG. 15,the template builder may enable a user to generate a processingactivity-based questionnaire template that includes one or more sections1520 related to the processing activity (e.g., business processinformation, personal data, source, storage, destinations, access anduse, etc.). As may be understood in light of this disclosure, the systemmay be configured to substantially automatically generate a processingactivity-based questionnaire template based at least in part on the oneor more unpopulated inventory attributes related to the processingactivity (e.g., as discussed above). The system may, for example, beconfigured to generate a template that is configured to populate the oneor more unpopulated attributes (e.g., by eliciting responses, via aquestionnaire to one or more questions that are mapped to the attributeswithin the data inventory).

In various embodiments, the system is configured to enable a user tomodify a default template (e.g., or a system-created template) by, forexample, adding additional sections, adding one or more additionalquestions to a particular section, etc. In various embodiments, thesystem may provide one or more tools for modifying the template. Forexample, in the embodiment shown in FIG. 15, the system may provide auser with a draft and drop question template 1510, from which the usermay select a question type (e.g., textbox, multiple choice, assetattributes, data subjects, etc.). The system may be further configuredto enable a user to publish a completed template (e.g., for use in aparticular assessment). In any embodiment described herein, the systemmay be configured to substantially automatically publish the template.

In various embodiments, a template for a processing activity mayinclude, for example: (1) one or more questions related to the type ofbusiness process that involves a particular data asset; (2) one or morequestions regarding what type of personal data is acquired from datasubjects for use by a particular data asset; (3) one or more questionsrelated to a source of the acquired personal data; (4) one or morequestions related to how and/or where the personal data will be storedand/or for how long; (5) one or more questions related to one or moreother data assets that the personal data will be transferred to; and/or(6) one or more questions related to who will have the ability to accessand/or use the personal data.

Continuing to FIG. 16, an exemplary screen display 1600 depicts alisting of assets 1610 for a particular entity. These may, for example,have been identified as part of the data model generation systemdescribed above. As may be understood from this figure, a user mayselect a drop-down indicator 1615 to view more information about aparticular asset. In the exemplary embodiment shown in FIG. 16, thesystem stores the managing organization group for the “New Asset”, butis missing some additional information (e.g., such as a description 1625of the asset). In order to fill out the missing inventory attributes forthe “New Asset”, the system, in particular embodiments, is configured toenable a user to select a Send Assessment indicia 1620 in order totransmit an assessment related to the selected asset to an individualtasked with providing one or more pieces of information related to theasset (e.g., a manager, or other individual with knowledge of the one ormore inventory attributes).

In response to the user selecting the Send Assessment indicia 1620, thesystem may create the assessment based at least in part on a templateassociated with the asset and transmit the assessment to a suitableindividual for completion (e.g., and/or transmit a request to theindividual to complete the assessment).

FIG. 17 depicts an exemplary assessment transmission interface 1700 viawhich a user can transmit one or more assessments for completion. Asshown in this figure, the user may assign a respondent, provide adeadline, indicate a reminder time, and provide one or more commentsusing an assessment request interface 1710. The user may then select aSend Assessment(s) indicia 1720 in order to transmit the assessment.

FIG. 18 depicts an exemplary assessment 1800 which a user may encounterin response to receiving a request to complete the assessment asdescribed above with respect to FIGS. 16 and 17. As shown in FIG. 18,the assessment 1800 may include one or more questions that map to theone or more unpopulated attributes for the asset shown in FIG. 16. Forexample, the one or more questions may include a question related to adescription of the asset, which may include a free form text box 1820for providing a description of the asset. FIG. 19 depicts an exemplaryscreen display 1900 with the text box 1920 completed, where thedescription includes a value of “Value_1”. As shown in FIGS. 18 and 19,the user may have renamed “New Asset” (e.g., which may have included adefault or placeholder name) shown in FIGS. 16 and 17 to “7th Asset.”

Continuing to FIG. 20, the exemplary screen display 2000 depicts thelisting of assets 2010 from FIG. 16 with some additional attributespopulated. For example, the Description 2025 (e.g., “Value_1”) providedin FIG. 19 has been added to the inventory. As may be understood inlight of this disclosure, in response to a user providing thedescription via the assessment shown in FIGS. 18 and 19, the system maybe configured to map the provided description to the attribute valueassociated with the description of the asset in the data inventory. Thesystem may have then modified the data inventory for the asset toinclude the description attribute. In various embodiments, the system isconfigured to store the modified data inventory as part of a data model(e.g., in computer memory).

FIGS. 21-24 depict exemplary screen displays showing exemplary questionsthat make up part of a processing activity questionnaire (e.g.,assessment). FIG. 21 depicts an exemplary interface 2100 for respondingto a first question 2110 and a second question 2120. As shown in FIG.21, the first question 2110 relates to whether the processing activityis a new or existing processing activity. The first question 2110 shownin FIG. 21 is a multiple-choice question. The second question 2120relates to whether the organization is conducting the activity on behalfof another organization. As shown in this figure, the second question2120 includes both a multiple-choice portion and a free-form responseportion.

As discussed above, in various embodiments, the system may be configuredto modify a questionnaire in response to (e.g., based on) one or moreresponses provided by a user completing the questionnaire. In particularembodiments, the system is configured to modify the questionnairesubstantially on-the-fly (e.g., as the user provides each particularanswer). FIG. 22 depicts an interface 2200 that includes a secondquestion 2220 that differs from the second question 2120 shown in FIG.21. As may be understood in light of this disclosure, in response to theuser providing a response to the first question 2110 in FIG. 21 thatindicates that the processing activity is a new processing activity, thesystem may substantially automatically modify the second question 2120from FIG. 21 to the second question 2220 from FIG. 22 (e.g., such thatthe second question 2220 includes one or more follow up questions orrequests for additional information based on the response to the firstquestion 2110 in FIG. 21).

As shown in FIG. 22, the second question 2220 requests a description ofthe activity that is being pursued. In various embodiments (e.g., suchas if the user had selected that the processing activity was an existingone), the system may not modify the questionnaire to include the secondquestion 2220 from FIG. 22, because the system may already storeinformation related to a description of the processing activity atissue. In various embodiments, any suitable question described hereinmay include a tooltip 2225 on a field name (e.g., which may provide oneor more additional pieces of information to guide a user's response tothe questionnaire and/or assessment).

FIGS. 23 and 24 depict additional exemplary assessment questions. Thequestions shown in these figures relate to, for example, particular dataelements processed by various aspects of a processing activity.

FIG. 25 depicts a dashboard 2500 that includes an accounting of one ormore assessments that have been completed, are in progress, or requirecompletion by a particular organization. The dashboard 2500 shown inthis figure is configured to provide information relate to the status ofone or more outstanding assessments. As may be understood in light ofthis disclosure, because of the volume of assessment requests, it may benecessary to utilize one or more third party organizations to facilitatea timely completion of one or more assessment requests. In variousembodiments, the dashboard may indicate that, based on a fact that anumber of assessments are still in progress or incomplete, that aparticular data model for an entity, data asset, processing activity,etc. remains incomplete. In such embodiments, an incomplete nature of adata model may raise one or more flags or indicate a risk that an entitymay not be in compliance with one or more legal or industry requirementsrelated to the collection, storage, and/or processing of personal data.

Intelligent Identity Scanning Module

Turning to FIG. 26, in particular embodiments, the Intelligent IdentityScanning Module 2600 is configured to scan one or more data sources toidentify personal data stored on one or more network devices for aparticular organization, analyze the identified personal data, andclassify the personal data (e.g., in a data model) based at least inpart on a confidence score derived using one or more machine learningtechniques. The confidence score may be and/or comprise, for example, anindication of the probability that the personal data is actuallyassociated with a particular data subject (e.g., that there is at leastan 80% confidence level that a particular phone number is associatedwith a particular individual.)

When executing the Intelligent Identity Scanning Module 2600, the systembegins, at Step 2610, by connecting to one or more databases or otherdata structures, and scanning the one or more databases to generate acatalog of one or more individuals and one or more pieces of personalinformation associated with the one or more individuals. The system may,for example, be configured to connect to one or more databasesassociated with a particular organization (e.g., one or more databasesthat may serve as a storage location for any personal or other datacollected, processed, etc. by the particular organization, for example,as part of a suitable processing activity. As may be understood in lightof this disclosure, a particular organization may use a plurality of oneor more databases (e.g., the One or More Databases 140 shown in FIG. 1),a plurality of servers (e.g., the One or More Third Party Servers 160shown in FIG. 1), or any other suitable data storage location in orderto store personal data and other data collected as part of any suitableprivacy campaign, privacy impact assessment, processing activity, etc.

In particular embodiments, the system is configured to scan the one ormore databases by searching for particular data fields comprising one ormore pieces of information that may include personal data. The systemmay, for example, be configured to scan and identify one of more piecesof personal data such as: (1) name; (2) address; (3) telephone number;(4) e-mail address; (5) social security number; (6) informationassociated with one or more credit accounts (e.g., credit card numbers);(7) banking information; (8) location data; (9) internet search history;(10) non-credit account data; and/or (11) any other suitable personalinformation discussed herein. In particular embodiments, the system isconfigured to scan for a particular type of personal data (e.g., or oneor more particular types of personal data).

The system may, in various embodiments, be further configured togenerate a catalog of one or more individuals that also includes one ormore pieces of personal information (e.g., personal data) identified forthe individuals during the scan. The system may, for example, inresponse to discovering one or more pieces of personal data in aparticular storage location, identify one or more associations betweenthe discovered pieces of personal data. For example, a particulardatabase may store a plurality of individuals' names in association withtheir respective telephone numbers. One or more other databases mayinclude any other suitable information.

The system may, for example, generate the catalog to include anyinformation associated with the one or more individuals identified inthe scan. The system may, for example, maintain the catalog in anysuitable format (e.g., a data table, etc.).

Continuing to Step 2620, the system is configured to scan one or morestructured and/or unstructured data repositories based at least in parton the generated catalog to identify one or more attributes of dataassociated with the one or more individuals. The system may, forexample, be configured to utilize information discovered during theinitial scan at Step 2610 to identify the one or more attributes of dataassociated with the one or more individuals.

For example, the catalog generated at Step 2610 may include a name,address, and phone number for a particular individual. The system may beconfigured, at Step 2620, to scan the one or more structured and/orunstructured data repositories to identify one or more attributes thatare associated with one or more of the particular individual's name,address and/or phone number. For example, a particular data repositorymay store banking information (e.g., a bank account number and routingnumber for the bank) in association with the particular individual'saddress. In various embodiments, the system may be configured toidentify the banking information as an attribute of data associated withthe particular individual. In this way, the system may be configured toidentify particular data attributes (e.g., one or more pieces ofpersonal data) stored for a particular individual by identifying theparticular data attributes using information other than the individual'sname.

Returning to Step 2630, the system is configured to analyze andcorrelate the one or more attributes and metadata for the scanned one ormore structured and/or unstructured data repositories. In particularembodiments, the system is configured to correlate the one or moreattributes with metadata for the associated data repositories from whichthe system identified the one or more attributes. In this way, thesystem may be configured to store data regarding particular datarepositories that store particular data attributes.

In particular embodiments, the system may be configured tocross-reference the data repositories that are discovered to store oneor more attributes of personal data associated with the one or moreindividuals with a database of known data assets. In particularembodiments, the system is configured to analyze the data repositoriesto determine whether each data repository is part of an existing datamodel of data assets that collect, store, and/or process personal data.In response to determining that a particular data repository is notassociated with an existing data model, the system may be configured toidentify the data repository as a new data asset (e.g., via assetdiscovery), and take one or more actions (e.g., such as any suitableactions described herein) to generate and populate a data model of thenewly discovered data asset. This may include, for example: (1)generating a data inventory for the new data asset; (2) populating thedata inventory with any known attributes associated with the new dataasset; (3) identifying one or more unpopulated (e.g., unknown)attributes of the data asset; and (4) taking any suitable actiondescribed herein to populate the unpopulated data attributes.

In particular embodiments, the system my, for example: (1) identify asource of the personal data stored in the data repository that led tothe new asset discovery; (2) identify one or more relationships betweenthe newly discovered asset and one or more known assets; and/or (3) etc.

Continuing to Step 2640, the system is configured to use one or moremachine learning techniques to categorize one or more data elements fromthe generated catalog, analyze a flow of the data among the one or moredata repositories, and/or classify the one or more data elements basedon a confidence score as discussed below.

Continuing to Step 2650, the system, in various embodiments, isconfigured to receive input from a user confirming or denying acategorization of the one or more data elements, and, in response,modify the confidence score. In various embodiments, the system isconfigured to iteratively repeat Steps 2640 and 2650. In this way, thesystem is configured to modify the confidence score in response to auser confirming or denying the accuracy of a categorization of the oneor more data elements. For example, in particular embodiments, thesystem is configured to prompt a user (e.g., a system administrator,privacy officer, etc.) to confirm that a particular data element is, infact, associated with a particular individual from the catalog. Thesystem may, in various embodiments, be configured to prompt a user toconfirm that a data element or attribute discovered during one or moreof the scans above were properly categorized at Step 2640.

In particular embodiments, the system is configured to modify theconfidence score based at least in part on receiving one or moreconfirmations that one or more particular data elements or attributesdiscovered in a particular location during a scan are associated withparticular individuals from the catalog. As may be understood in lightof this disclosure, the system may be configured to increase theconfidence score in response to receiving confirmation that particulartypes of data elements or attributes discovered in a particular storagelocation are typically confirmed as being associated with particularindividuals based on one or more attributes for which the system wasscanning.

Exemplary Intelligent Identity Scanning Technical Platforms

FIG. 27 depicts an exemplary technical platform via which the system mayperform one or more of the steps described above with respect to theIntelligent Identity Scanning Module 2600. As shown in the embodiment inthis figure, an Intelligent Identity Scanning System 2600 comprises anIntelligent Identity Scanning Server 130, such as the IntelligentIdentity Scanning Server 130 described above with respect to FIG. 1. TheIntelligent Identity Scanning Server 130 may, for example, comprise aprocessing engine (e.g., one or more computer processors). In someembodiments, the Intelligent Identity Scanning Server 130 may includeany suitable cloud hosted processing engine (e.g., one or morecloud-based computer servers). In particular embodiments, theIntelligent Identity Scanning Server 130 is hosted in a Microsoft Azurecloud.

In particular embodiments, the Intelligent Identity Scanning Server 130is configured to sit outside one or more firewalls (e.g., such as thefirewall 195 shown in FIG. 26). In such embodiments, the IntelligentIdentity Scanning Server 130 is configured to access One or More RemoteComputing Devices 150 through the Firewall 195 (e.g., one or morefirewalls) via One or More Networks 115 (e.g., such as any of the One orMore Networks 115 described above with respect to FIG. 1).

In particular embodiments, the One or More Remote Computing Devices 150include one or more computing devices that make up at least a portion ofone or more computer networks associated with a particular organization.In particular embodiments, the one or more computer networks associatedwith the particular organization comprise one or more suitable servers,one or more suitable databases, one or more privileged networks, and/orany other suitable device and/or network segment that may store and/orprovide for the storage of personal data. In the embodiment shown inFIG. 27, the one or more computer networks associated with theparticular organization may comprise One or More Third Party Servers160, One or More Databases 140, etc. In particular embodiments, the Oneor More Remote Computing Devices 150 are configured to access one ormore segments of the one or more computer networks associated with theparticular organization. In some embodiments, the one or more computernetworks associated with the particular organization comprise One orMore Privileged Networks 165. In still any embodiment described herein,the one or more computer networks comprise one or more network segmentsconnected via one or more suitable routers, one or more suitable networkhubs, one or more suitable network switches, etc.

As shown in FIG. 27, various components that make up one or more partsof the one or more computer networks associated with the particularorganization may store personal data (e.g., such as personal data storedon the One or More Third Party Servers 160, the One or More Databases140, etc.). In various embodiments, the system is configured to performone or more steps related to the Intelligent Identity Scanning Server2600 in order to identify the personal data for the purpose ofgenerating the catalog of individuals described above (e.g., and/oridentify one or more data assets within the organization's network thatstore personal data)

As further shown in FIG. 27, in various embodiments, the One or MoreRemote Computing Devices 150 may store a software application (e.g., theIntelligent Identity Scanning Module). In such embodiments, the systemmay be configured to provide the software application for installationon the One or More Remote Computing Devices 150. In particularembodiments, the software application may comprise one or more virtualmachines. In particular embodiments, the one or more virtual machinesmay be configured to perform one or more of the steps described abovewith respect to the Intelligent Identity Scanning Module 2600 (e.g.,perform the one or more steps locally on the One or More RemoteComputing Devices 150).

In various embodiments, the one or more virtual machines may have thefollowing specifications: (1) any suitable number of cores (e.g., 4, 6,8, etc.); (2) any suitable amount of memory (e.g., 4 GB, 8 GB, 16 GBetc.); (3) any suitable operating system (e.g., CentOS 7.2); and/or (4)any other suitable specification. In particular embodiments, the one ormore virtual machines may, for example, be used for one or more suitablepurposes related to the Intelligent Identity Scanning System 2700. Theseone or more suitable purposes may include, for example, running any ofthe one or more modules described herein, storing hashed and/ornon-hashed information (e.g., personal data, personally identifiabledata, catalog of individuals, etc.), storing and running one or moresearching and/or scanning engines (e.g., Elasticsearch), etc.

In various embodiments, the Intelligent Identity Scanning System 2700may be configured to distribute one or more processes that make up partof the Intelligent Identity Scanning Process (e.g., described above withrespect to the Intelligent Identity Scanning Module 1800). The one ormore software applications installed on the One or more Remote ComputingDevices 150 may, for example, be configured to provide access to the oneor more computer networks associated with the particular organization tothe Intelligent Identity Scanning Server 130. The system may then beconfigured to receive, from the One or more Remote Computing Devices 150at the Intelligent Identity Scanning Server 130, via the Firewall 195and One or More Networks 115, scanned data for analysis.

In particular embodiments, the Intelligent Identity Scanning System 2700is configured to reduce an impact on a performance of the One or MoreRemote Computing Devices 150, One or More Third Party Servers 160 andother components that make up one or more segments of the one or morecomputer networks associated with the particular organization. Forexample, in particular embodiments, the Intelligent Identity ScanningSystem 2700 may be configured to utilize one or more suitable bandwidththrottling techniques. In any embodiment described herein, theIntelligent Identity Scanning System 2700 is configured to limitscanning (e.g., any of the one or more scanning steps described abovewith respect to the Intelligent Identity Scanning Module 2600) and otherprocessing steps (e.g., one or more steps that utilize one or moreprocessing resources) to non-peak times (e.g., during the evening,overnight, on weekends and/or holidays, etc.). In any embodimentdescribed herein, the system is configured to limit performance of suchprocessing steps to backup applications and data storage locations. Thesystem may, for example, use one or more sampling techniques to decreasea number of records required to scan during the personal data discoveryprocess.

FIG. 28 depicts an exemplary asset access methodology that the systemmay utilize in order to access one or more network devices that maystore personal data (e.g., or other personally identifiableinformation). As may be understood from this figure, the system may beconfigured to access the one or more network devices using a locallydeployed software application (e.g., such as the software applicationdescribed immediately above). In various embodiments, the softwareapplication is configured to route identity scanning traffic through oneor more gateways, configure one or more ports to accept one or moreidentity scanning connections, etc.

As may be understood from this figure, the system may be configured toutilize one or more credential management techniques to access one ormore privileged network portions. The system may, in response toidentifying particular assets or personally identifiable information viaa scan, be configured to retrieve schema details such as, for example,an asset ID, Schema ID, connection string, credential reference URL,etc. In this way, the system may be configured to identify and store alocation of any discovered assets or personal data during a scan.

Data Subject Access Request Fulfillment Module

Turning to FIG. 29, in particular embodiments, a Data Subject AccessRequest Fulfillment Module 2900 is configured to receive a data subjectaccess request, process the request, and fulfill the request based atleast in part on one or more request parameters. In various embodiments,an organization, corporation, etc. may be required to provideinformation requested by an individual for whom the organization storespersonal data within a certain time period (e.g., 30 days). As aparticular example, an organization may be required to provide anindividual with a listing of, for example: (1) any personal data thatthe organization is processing for an individual, (2) an explanation ofthe categories of data being processed and the purpose of suchprocessing; and/or (3) categories of third parties to whom the data maybe disclosed.

Various privacy and security policies (e.g., such as the EuropeanUnion's General Data Protection Regulation, and other such policies) mayprovide data subjects (e.g., individuals, organizations, or otherentities) with certain rights related to the data subject's personaldata that is collected, stored, or otherwise processed by anorganization. These rights may include, for example: (1) a right toobtain confirmation of whether a particular organization is processingtheir personal data; (2) a right to obtain information about the purposeof the processing (e.g., one or more reasons for which the personal datawas collected); (3) a right to obtain information about one or morecategories of data being processed (e.g., what type of personal data isbeing collected, stored, etc.); (4) a right to obtain information aboutone or more categories of recipients with whom their personal data maybe shared (e.g., both internally within the organization or externally);(5) a right to obtain information about a time period for which theirpersonal data will be stored (e.g., or one or more criteria used todetermine that time period); (6) a right to obtain a copy of anypersonal data being processed (e.g., a right to receive a copy of theirpersonal data in a commonly used, machine-readable format); (7) a rightto request erasure (e.g., the right to be forgotten), rectification(e.g., correction or deletion of inaccurate data), or restriction ofprocessing of their personal data; and (8) any other suitable rightsrelated to the collection, storage, and/or processing of their personaldata (e.g., which may be provided by law, policy, industry ororganizational practice, etc.).

As may be understood in light of this disclosure, a particularorganization may undertake a plurality of different privacy campaigns,processing activities, etc. that involve the collection and storage ofpersonal data. In some embodiments, each of the plurality of differentprocessing activities may collect redundant data (e.g., may collect thesame personal data for a particular individual more than once), and maystore data and/or redundant data in one or more particular locations(e.g., on one or more different servers, in one or more differentdatabases, etc.). In this way, a particular organization may storepersonal data in a plurality of different locations which may includeone or more known and/or unknown locations. As such, complying withparticular privacy and security policies related to personal data (e.g.,such as responding to one or more requests by data subjects related totheir personal data) may be particularly difficult (e.g., in terms ofcost, time, etc.). In particular embodiments, a data subject accessrequest fulfillment system may utilize one or more data model generationand population techniques (e.g., such as any suitable techniquedescribed herein) to create a centralized data map with which the systemcan identify personal data stored, collected, or processed for aparticular data subject, a reason for the processing, and any otherinformation related to the processing.

Turning to FIG. 21, when executing the Data Subject Access RequestModule 2100, the system begins, at Step 2110, by receiving a datasubject access request. In various embodiments, the system receives therequest via a suitable web form. In certain embodiments, the requestcomprises a particular request to perform one or more actions with anypersonal data stored by a particular organization regarding therequestor. For example, in some embodiments, the request may include arequest to view one or more pieces of personal data stored by the systemregarding the requestor. In any embodiment described herein, the requestmay include a request to delete one or more pieces of personal datastored by the system regarding the requestor. In still any embodimentdescribed herein, the request may include a request to update one ormore pieces of personal data stored by the system regarding therequestor. In still any embodiment described herein, the request mayinclude a request based on any suitable right afforded to a datasubject, such as those discussed above.

Continuing to Step 2120, the system is configured to process the requestby identifying and retrieving one or more pieces of personal dataassociated with the requestor that are being processed by the system.For example, in various embodiments, the system is configured toidentify any personal data stored in any database, server, or other datarepository associated with a particular organization. In variousembodiments, the system is configured to use one or more data models,such as those described above, to identify this personal data andsuitable related information (e.g., where the personal data is stored,who has access to the personal data, etc.). In various embodiments, thesystem is configured to use intelligent identity scanning (e.g., asdescribed above) to identify the requestor's personal data and relatedinformation that is to be used to fulfill the request.

In still any embodiment described herein, the system is configured touse one or more machine learning techniques to identify such personaldata. For example, the system may identify particular stored personaldata based on, for example, a country in which a website that the datasubject request was submitted is based, or any other suitableinformation.

In particular embodiments, the system is configured to scan and/orsearch one or more existing data models (e.g., one or more current datamodels) in response to receiving the request in order to identify theone or more pieces of personal data associated with the requestor. Thesystem may, for example, identify, based on one or more data inventories(e.g., one or more inventory attributes) a plurality of storagelocations that store personal data associated with the requestor. In anyembodiment described herein, the system may be configured to generate adata model or perform one or more scanning techniques in response toreceiving the request (e.g., in order to automatically fulfill therequest).

Returning to Step 2130, the system is configured to take one or moreactions based at least in part on the request. In some embodiments, thesystem is configured to take one or more actions for which the requestwas submitted (e.g., display the personal data, delete the personaldata, correct the personal data, etc.). In particular embodiments, thesystem is configured to take the one or more actions substantiallyautomatically. In particular embodiments, in response a data subjectsubmitting a request to delete their personal data from anorganization's systems, the system may: (1) automatically determinewhere the data subject's personal data is stored; and (2) in response todetermining the location of the data (which may be on multiple computingsystems), automatically facilitate the deletion of the data subject'spersonal data from the various systems (e.g., by automatically assigninga plurality of tasks to delete data across multiple business systems toeffectively delete the data subject's personal data from the systems).In particular embodiments, the step of facilitating the deletion maycomprise, for example: (1) overwriting the data in memory; (2) markingthe data for overwrite; (2) marking the data as free (e.g., and deletinga directory entry associated with the data); and/or (3) any othersuitable technique for deleting the personal data. In particularembodiments, as part of this process, the system uses an appropriatedata model (see discussion above) to efficiently determine where all ofthe data subject's personal data is stored.

Data Subject Access Request User Experience

FIGS. 30-31 depict exemplary screen displays that a user may view whensubmitting a data subject access request. As shown in FIG. 30, a website30000 associated with a particular organization may include auser-selectable indicium 3005 for submitting a privacy-related request.A user desiring to make such a request may select the indicia 3005 inorder to initiate the data subject access request process.

FIG. 31 depicts an exemplary data subject access request form in both anunfilled and filled out state. As shown in this figure, the system mayprompt a user to provide information such as, for example: (1) what typeof requestor the user is (e.g., employee, customer, etc.); (2) what therequest involves (e.g., requesting info, opting out, deleting data,updating data, etc.); (3) first name; (4) last name; (5) email address;(6) telephone number; (7) home address; and/or (8) one or more detailsassociated with the request.

As discussed in more detail above, a data subject may submit a subjectaccess request, for example, to request a listing of any personalinformation that a particular organization is currently storingregarding the data subject, to request that the personal data bedeleted, to opt out of allowing the organization to process the personaldata, etc.

Alternative Embodiment

In particular embodiments, a data modeling or other system describedherein may include one or more features in addition to those described.Various such alternative embodiments are described below.

Processing Activity and Data Asset Assessment Risk Flagging

In particular embodiments, the questionnaire template generation systemand assessment system described herein may incorporate one or more riskflagging systems. FIGS. 32-35 depict exemplary user interfaces thatinclude risk flagging of particular questions within a processingactivity assessment. As may be understood from these figures, a user mayselect a flag risk indicium to provide input related to a description ofrisks and mitigation of a risk posed by one or more inventory attributesassociated with the question. As shown in these figures, the system maybe configured to substantially automatically assign a risk to aparticular response to a question in a questionnaire. In variousembodiments, the assigned risk is determined based at least in part onthe template from which the assessment was generated.

In particular embodiments, the system may utilize the risk levelassigned to particular questionnaire responses as part of a riskanalysis of a particular processing activity or data asset. Varioustechniques for assessing the risk of various privacy campaigns aredescribed in U.S. patent application Ser. No. 15/256,419, filed Sep. 2,2016, entitled “Data processing systems and methods for operationalizingprivacy compliance and assessing the risk of various respective privacycampaigns,” which is hereby incorporated herein in its entirety.

Centralized Repository of Personally Identifiable Information (PII)Overview

A centralized data repository system, in various embodiments, isconfigured to provide a central data-storage repository (e.g., one ormore servers, databases, etc.) for the centralized storage of personallyidentifiable information (PII) and/or personal data for one or moreparticular data subjects. In particular embodiments, the centralizeddata repository may enable the system to populate one or more datamodels (e.g., using one or more suitable techniques described above)substantially on-the-fly (e.g., as the system collects, processes,stores, etc. personal data regarding a particular data subject). In thisway, in particular embodiments, the system is configured to maintain asubstantially up-to-date data model for a plurality of data subjects(e.g., each particular data subject for whom the system collects,processes, stores, etc. personal data). The system may then beconfigured to substantially automatically respond to one or more dataaccess requests by a data subject (e.g., individual, entity,organization, etc.), for example, using the substantially up-to-datedata model. In particular embodiments, the system may be configured torespond to the one or more data access requests using any suitabletechnique described herein.

As may be understood in light of this disclosure, a particularorganization may undertake a plurality of different privacy campaigns,processing activities, etc. that involve the collection and storage ofpersonal data. In some embodiments, each of the plurality of differentprocessing activities may collect redundant data (e.g., may collect thesame personal data for a particular individual more than once), and maystore data and/or redundant data in a plurality of different locations(e.g., on one or more different servers, in one or more differentdatabases, etc.). In this way, a particular organization may storepersonal data in a plurality of different locations which may includeone or more known and/or unknown locations. As such, complying withparticular privacy and security policies related to personal data (e.g.,such as responding to one or more requests by data subjects related totheir personal data) may be particularly difficult (e.g., in terms ofcost, time, etc.). Accordingly, utilizing and maintaining a centralizeddata repository for PII may enable the system to more quickly andaccurately respond to data subject access requests and other requestsrelated to collected, stored, and processed personal data. In particularembodiments, the centralized data repository may include one or morethird party data repositories (e.g., one or more third party datarepositories maintained on behalf of a particular entity that collects,stores, and/or processes personal data).

In various embodiments, a third-party data repository system isconfigured to facilitate the receipt and centralized storage of personaldata for each of a plurality of respective data subjects. In particularembodiments, the system may be configured to: (1) receive personal dataassociated with a particular data subject (e.g., a copy of the data, alink to a location of where the data is stored, etc.); and (2) store thepersonal data in a suitable data format (e.g., a data model, a referencetable, etc.) for later retrieval. In any embodiment described herein,the system may be configured to receive an indication that personal datahas been collected regarding a particular data subject (e.g., collectedby a first party system, a software application utilized by a particularentity, etc.).

In particular embodiments, the third party data repository system isconfigured to: (1) receive an indication that a first party system(e.g., entity) has collected and/or processed a piece of personal datafor a data subject; (2) determine a location in which the first partysystem has stored the piece of personal data; (3) optionally digitallystore (e.g., in computer memory) a copy of the piece of personal dataand associate, in memory, the piece of personal data with the datasubject; and (4) optionally digitally store an indication of the storagelocation utilized by the first party system for the piece of personaldata. In particular embodiments, the system is configured to provide acentralized database, for each particular data subject (e.g., eachparticular data subject about whom a first party system collects or hascollected personally identifiable information), of any personal dataprocessed and/or collected by a particular entity.

In particular embodiments, a third-party data repository system isconfigured to interface with a consent receipt management system (e.g.,such as the consent receipt management system described below). Inparticular embodiments, the system may, for example: (1) receive anindication of a consent receipt having an associated unique subjectidentifier and one or more receipt definitions (e.g., such as anysuitable definition described herein); (2) identify, based at least inpart on the one or more receipt definitions, one or more pieces ofrepository data associated with the consent receipt (e.g., one or moredata elements or pieces of personal data for which the consent receiptprovides consent to process; a storage location of the one or more dataelements for which the consent receipt provides consent to process;etc.); (3) digitally store the unique subject identifier in one or moresuitable data stores; and (4) digitally associate the unique subjectidentifier with the one or more pieces of repository data. In particularembodiments, the system is configured to store the personal dataprovided as part of the consent receipt in association with the uniquesubject identifier.

In particular embodiments, the system is configured to, for each storedunique subject identifier: (1) receive an indication that new personaldata has been provided by or collected from a data subject associatedwith the unique subject identifier (e.g., provided to an entity ororganization that collects and/or processes personal data); and (2) inresponse to receiving the indication, storing the new personal data(e.g., or storing an indication of a storage location of the newpersonal data by the entity) in association with the unique subjectidentifier. In this way, as an entity collects additional data for aparticular unique data subject (e.g., having a unique subjectidentifier, hash, etc.), the third party data repository system isconfigured to maintain a centralized database of data collected, stored,and or processed for each unique data subject (e.g., indexed by uniquesubject identifier). The system may then, in response to receiving adata subject access request from a particular data subject, fulfill therequest substantially automatically (e.g., by providing a copy of thepersonal data, deleting the personal data, indicating to the entity whatpersonal data needs to be deleted from their system and where it islocated, etc.). The system may, for example, automatically fulfill therequest by: (1) identifying the unique subject identifier associatedwith the unique data subject making the request; and (2) retrieving anyinformation associated with the unique data subject based on the uniquesubject identifier.

Exemplary Centralized Data Repository System Architecture

FIG. 36 is a block diagram of a centralized data repository system 3600according to a particular embodiment. In various embodiments, thecentralized data repository system 3600 is part of a privacy compliancesystem (also referred to as a privacy management system), or othersystem, which may, for example, be associated with a particularorganization and be configured to aid in compliance with one or morelegal or industry regulations related to the collection and storage ofpersonal data. In any embodiment described herein, the centralized datarepository system 3600 is a stand-alone system that is configured tointerface with one or more first party data management or other systemsfor the purpose of maintaining a centralized data repository of personaldata collected, stored, and/or processed by each of the one or morefirst party data systems.

As may be understood from FIG. 36, the centralized data repositorysystem 3600 includes one or more computer networks 115, One or MoreCentralized Data Repository Servers 3610, a Consent Receipt ManagementServer 3620, One or More First Party System Servers 3630, One or MoreDatabases 140 or other data structures, and one or more remote datasubject computing devices 3650 (e.g., a desktop computer, laptopcomputer, tablet computer, smartphone, etc.). In particular embodiments,the One or More Centralized Data Repository Servers 3610, ConsentReceipt Management Server 3620, One or More First Party System Servers3630, One or More Databases 140 or other data structures, and one ormore remote data subject computing devices 3650. Although in theembodiment shown in FIG. 36, the One or More Centralized Data RepositoryServers 3610, Consent Receipt Management Server 3620, One or More FirstParty System Servers 3630, One or More Databases 140 or other datastructures, and one or more remote data subject computing devices 3650are shown as separate servers, it should be understood that in anyembodiment described herein, one or more of these servers and/orcomputing devices may comprise a single server, a plurality of servers,one or more cloud-based servers, or any other suitable configuration.

In particular embodiments, the One or More Centralized Data RepositoryServers 3610 may be configured to interface with the One or More FirstParty System Servers 3630 to receive any of the indications or personaldata (e.g., for storage) described herein. The One or More CentralizedData Repository Servers 3610 and One or More First Party System Servers3630 may, for example, interface via a suitable application programminginterface, direct connection, etc. In a particular embodiment, the Oneor More Centralized Data Repository Servers 3610 comprise the ConsentReceipt Management Server 3620.

In a particular example, a data subject may provide one or more piecesof personal data via the One or More Remote Data Subject ComputingDevices 3650 to the One or More First Party System Servers 3630. Thedata subject may, for example, complete a webform on a website hosted onthe One or More First Party System Servers 3630. The system may then, inresponse to receiving the one or more pieces of personal data at the Oneor More First Party System Servers 3630, transmit an indication to theOne or More Centralized Data Repository Servers 3610 that the One orMore First Party System Servers 3630 have collected, stored, and/orprocessed the one or more pieces of personal data. In response toreceiving the indication, the One or More Centralized Data RepositoryServers 3610 may then store the one or more pieces of personal data(e.g., a copy of the data, an indication of the storage location of thepersonal data in the One or More First Party System Servers 3630, etc.)in a centralized data storage location (e.g., in One or More Databases140, on the One or More Centralized Data Repository Servers 3610, etc.).

Centralized Data Repository Module

Various functionality of the centralized data repository system 3600 maybe implemented via a Centralized Data Repository Module 3700. Thesystem, when executing certain steps of the Centralized Data RepositoryModule, may be configured to generate, a central repository of personaldata on behalf of an entity, and populate the central repository withpersonal data as the entity collects, stores and/or processes thepersonal data. In particular embodiments, the system is configured toindex the personal data within the central repository by data subject.

FIG. 37 depicts a Centralized Data Repository Module 3700 according to aparticular embodiment. The system, when executing the Centralized DataRepository Module 3700, begins, at Step 3710, by receiving a request togenerate a central repository of personal data on behalf of an entity.In particular embodiments, the system is a third-party system thatreceives a request from the entity to generate and maintain a centralrepository (e.g., third party repository) of personal data that theentity collects, stores, and or processes.

In particular embodiments, the system, in response to receiving therequest, is configured to generate the central repository by: (1)designating at least a portion of one or more data stores for thestorage of the personal data, information about the data subjects aboutwhom the personal data is collected, etc.; (2) initiating a connectionbetween the central repository and one or more data systems operated bythe entity (e.g., one or more first party systems); (3) etc.

Continuing to Step 3720, the system is configured to generate, for eachdata subject about whom the entity collects, receives, and/or processespersonal data, a unique identifier. The system may, for example: (1)receive an indication that a first party system has collected, stored,and/or processed a piece of personal data; (2) identify a data subjectassociated with the piece of personal data; (3) determine whether thecentral repository system is currently storing data associated with thedata subject; and (4) in response to determining that the centralrepository system is not currently storing data associated with the datasubject (e.g., because the data subject is a new data subject),generating the unique identifier. In various embodiments, the system isconfigured to assign a unique identifier for each data subject aboutwhom the first party system has previously collected, stored, and/orprocessed personal data.

In particular embodiments, the unique identifier may include any uniqueidentifier such as, for example: (1) any of the one or more pieces ofpersonal data collected, stored, and/or processed by the system (e.g.,name, first name, last name, full name, address, phone number, e-mailaddress, etc.); (2) a unique string or hash comprising any suitablenumber of numerals, letters, or combination thereof; and/or (3) anyother identifier that is sufficiently unique to distinguish between afirst and second data subject for the purpose of subsequent dataretrieval.

In particular embodiments, the system is configured to assign apermanent identifier to each particular data subject. In any embodimentdescribed herein, the system is configured to assign one or moretemporary unique identifiers to the same data subject.

In particular embodiments, the unique identifier may be based at leastin part on the unique receipt key and/or unique subject identifierdiscussed below with respect to the consent receipt management system.As may be understood in light of this disclosure, when receiving consentform a data subject to process, collect, and at least store one or moreparticular types of personal data associated with the data subject, thesystem is configured to generate a unique ID to memorialize the consentand provide authorization for the system to collect the subject's data.In any embodiment described herein, the system may be configured toutilize any unique ID generated for the purposes of tracking datasubject consent as a unique identifier in the context of the centralrepository system described herein.

In particular embodiments, the system is configured to continue to Step3730, and store the unique identifier in computer memory. In particularembodiments, the system is configured to store the unique identifier inan encrypted manner. In various embodiments, the system is configured tostore the unique identifier in any suitable location (e.g., the one ormore databases 140 described above).

In particular embodiments, the system is configured to store the uniqueidentifier as a particular file structure such as, for example, aparticular folder structure in which the system is configured to storeone or more pieces of personal data (e.g., or pointers to one or morepieces of personal data) associated with the unique identifier (e.g.,the data subject associated with the unique identifier). In anyembodiment described herein, the system is configured to store theunique identifier in any other suitable manner (e.g., in a suitable datatable, etc.).

Returning to Step 3740, the system is configured to receive anindication that one or more computer systems have received, collected orprocessed one or more pieces of personal data associated with a datasubject. In particular embodiments, the one or more computer systemsinclude any suitable computer system associated with a particularentity. In any embodiment described herein, the one or more computersystems comprise one or more software applications, data stores,databases, etc. that collect, process, and/or store data (e.g.,personally identifiable data) on behalf of the entity (e.g.,organization). In particular embodiments, the system is configured toreceive the indication through integration with the one or more computersystems. In a particular example, the system may provide a softwareapplication for installation on a system device that is configured totransmit the indication in response to the system receiving, collecting,and/or processing one or more pieces of personal data.

In particular embodiments, the system may receive the indication inresponse to: (1) a first party system, data store, software application,etc. receiving, collecting, storing, and or processing a piece of datathat includes personally identifying information; (2) a user registeringfor an account with a particular entity (e.g., an online account,employee account, social media account, e-mail account, etc.); (3) acompany storing information about one or more data subjects (e.g.,employee information, customer information, potential customerinformation, etc.; and/or (4) any other suitable indication that a firstentity or any computer system or software on the first entity's behalfhas collected, stored, and/or processed a piece of data that includes ormay include personally identifiable information.

As a particular example, the system may receive the indication inresponse to a user submitting a webform via a website operated by thefirst entity. The webform may include, for example, one or more fieldsthat include the user's e-mail address, billing address, shippingaddress, and payment information for the purposes of collected paymentdata to complete a checkout process on an e-commerce website. In thisexample, because the information submitted via the webform containspersonal data (e.g., personally identifiable data) the system, inresponse to receiving an indication that the user has submitted the atleast partially completed webform, may be configured to receive theindication described above with respect to Step 3740.

In various embodiments, a first party privacy management system or othersystem (e.g., privacy management system, marketing system, employeerecords database management system, etc.) may be configured to transmitan indication to the central repository system in response tocollecting, receiving, or processing one or more pieces of personal datapersonal data.

In some embodiments, the indication may include, for example: (1) anindication of the type of personal data collected; (2) a purpose forwhich the personal data was collected; (3) a storage location of thepersonal data by the first party system; and/or (4) any other suitableinformation related to the one or more pieces of personal data or thehandling of the personal data by the first party system. In particularembodiments, the system is configured to receive the indication via anapplication programming interface, a software application stored locallyon a computing device within a network that makes up the first partysystem, or in any other suitable manner.

Continuing to Step 3750, the central repository system is configured tostore, in computer memory, an indication of the personal data inassociation with the respective unique identifier. In variousembodiments, the central repository system comprises a component of afirst party system for the centralized storage of personal datacollected by one or more various distributed computing systems (e.g.,and software applications) operated by a particular entity for thepurpose of collecting, storing, and/or processing personal data. In anyembodiment described herein, the central repository system is athird-party data repository system that is separate from the one or morefirst party systems described above. In particular embodiments, forexample, a third-party data repository system may be configured tomaintain a central repository of personal data for a plurality ofdifferent entities.

In particular embodiments, the central repository system is configuredto store a copy of the personal data (e.g., store a digital copy of thepersonal data in computer memory associated with the central repositorysystem). In still any embodiment described herein, the centralrepository system is configured to store an indication of a storagelocation of the personal data within the first party system. Forexample, the system may be configured to store an indication of aphysical location of a particular storage location (e.g., a physicallocation of a particular computer server or other data store) and anindication of a location of the personal data in memory on thatparticular storage location (e.g., a particular path or filename of thepersonal data, a particular location in a spreadsheet, CSV file, orother suitable document, etc.).

In various embodiments, the system may be configured to confirm receiptof valid consent to collect, store, and/or process personal data fromthe data subject prior to storing the indication of the personal data inassociation with the respective unique identifier. In such embodiments,the system may be configured to integrate with (e.g., interface with) aconsent receipt management system (e.g., such as the consent receiptmanagement system described more fully below). In such embodiments, thesystem may be configured to: (1) receive the indication that the firstparty system has collected, stored, and/or processed a piece of personaldata; (2) identify, based at least in part on the piece of personaldata, a data subject associated with the piece of personal data; (3)determine, based at least in part on one or more consent receiptsreceived from the data subject (e.g., one or more valid receipt keysassociated with the data subject), and one or more pieces of informationassociated with the piece of personal data, whether the data subject hasprovided valid consent to collect, store, and/or process the piece ofpersonal data; (4) in response to determining that the data subject hasprovided valid consent, storing the piece of personal data in any mannerdescribed herein; and (5) in response to determining that the datasubject has not provided valid consent, deleting the piece of personaldata (e.g., not store the piece of personal data).

In particular embodiments, in response to determining that the datasubject has not provided valid consent, the system may be furtherconfigured to: (1) automatically determine where the data subject'spersonal data is stored (e.g., by the first party system); and (2) inresponse to determining the location of the data (which may be onmultiple computing systems), automatically facilitate the deletion ofthe data subject's personal data from the various systems (e.g., byautomatically assigning a plurality of tasks to delete data acrossmultiple business systems to effectively delete the data subject'spersonal data from the systems). In particular embodiments, the step offacilitating the deletion may comprise, for example: (1) overwriting thedata in memory; (2) marking the data for overwrite; (2) marking the dataas free (e.g., and deleting a directory entry associated with the data);and/or (3) any other suitable technique for deleting the personal data.

Next, at optional step 3760, the system is configured to take one ormore actions based at least in part on the data stored in associationwith the unique identifier. In particular embodiments, the one or moreactions may include, for example, responding to a data subject accessrequest initiated by a data subject (e.g., or other individual on thedata subject's behalf) associated with the unique identifier. In variousembodiments, the system is configured to identify the unique identifierassociated with the data subject making the data subject access requestbased on information submitted as part of the request.

Consent Receipt Management Systems

In particular embodiments, any entity (e.g., organization, company,etc.) that collects, stores, processes, etc. personal data may requireone or more of: (1) consent from a data subject from whom the personaldata is collected and/or processed; and/or (2) a lawful basis for thecollection and/or processing of the personal data. In variousembodiments, the entity may be required to, for example: (1) demonstratethat a data subject has freely given specific, informed, and unambiguousindication of the data subject's agreement to the processing of his orher personal data (e.g., in the form of a statement or clear affirmativeaction); (2) demonstrate that the entity received consent from a datasubject in a manner clearly distinguishable from other matters (e.g., inan intelligible and easily accessible form, using clear and plainlanguage, etc.); (3) enable a data subject to withdraw consent as easilyas the data subject can give consent; (4) separate a data subject'sconsent from performance under any contract unless such processing isnecessary for performance under the contract; etc.

In various embodiments, a consent receipt management system may beimplemented in the context of any suitable privacy management systemthat is configured to ensure compliance with one or more legal orindustry standards related to the collection and/or storage of privateinformation (e.g., such as personal data). Various privacy and securitypolicies (e.g., such as the European Union's General Data ProtectionRegulation, and other such policies) may provide data subjects (e.g.,individuals, organizations, or other entities) with certain rightsrelated to the data subject's personal data that is collected, stored,or otherwise processed by an organization. These rights may include, forexample: (1) a right to erasure of the data subject's personal data(e.g., in cases where no legal basis applies to the processing and/orcollection of the personal data; (2) a right to withdraw consent to theprocessing and/or collection of their personal data; (3) a right toreceive the personal data concerning the data subject, which he or shehas provided to an entity (e.g., organization), in a structured,commonly used and machine-readable format; and/or (4) any other rightwhich may be afforded to the data subject under any applicable legaland/or industry policy.

In particular embodiments, the consent receipt management system isconfigured to: (1) enable an entity to demonstrate that valid consenthas been obtained for each particular data subject for whom the entitycollects and/or processes personal data; and (2) enable one or more datasubjects to exercise one or more rights described herein.

The system may, for example, be configured to track data on behalf of anentity that collects and/or processes persona data related to: (1) whoconsented to the processing or collection of personal data (e.g., thedata subject themselves or a person legally entitled to consent on theirbehalf such as a parent, guardian, etc.); (2) when the consent was given(e.g., a date and time); (3) what information was provided to theconsenter at the time of consent (e.g., a privacy policy, what personaldata would be collected following the provision of the consent, for whatpurpose that personal data would be collected, etc.); (4) how consentwas received (e.g., one or more copies of a data capture form, webform,etc. via which consent was provided by the consenter); (5) when consentwas withdrawn (e.g., a date and time of consent withdrawal if theconsenter withdraws consent); and/or (6) any other suitable data relatedto receipt or withdrawal of consent.

In further embodiments, the system may be configured to provide datasubjects with a centralized interface that is configured to: (1) provideinformation regarding each of one or more valid consents that the datasubject has provided to one or more entities related to the collectionand/or processing of their personal data; (2) provide one or moreperiodic reminders regarding the data subject's right to withdrawpreviously given consent (e.g., every 6 months in the case ofcommunications data and metadata, etc.); (3) provide a withdrawalmechanism for the withdrawal of one or more previously provided validconsents (e.g., in a format that is substantially similar to a format inwhich the valid consent was given by the data subject); (4) refreshconsent when appropriate (e.g., the system may be configured to elicitupdated consent in cases where particular previously validly consentedto processing is used for a new purpose, a particular amount of time haselapsed since consent was given, etc.).

In particular embodiments, the system is configured to manage one ormore consent receipts between a data subject and an entity. In variousembodiments, a consent receipt may include a record (e.g., a data recordstored in memory and associated with the data subject) of consent, forexample, as a transactional agreement where the data subject is alreadyidentified or identifiable as part of the data processing that resultsfrom the provided consent. In any embodiment described herein, thesystem may be configured to generate a consent receipt in response to adata subject providing valid consent. In some embodiments, the system isconfigured to determine whether one or more conditions for valid consenthave been met prior to generating the consent receipt.

Exemplary Consent Receipt Data Flow

FIG. 38 depicts an exemplary data flow that a consent receipt managementsystem may utilize in the recordation and management of one or moreconsent receipts. In particular embodiments, a third-party consentreceipt management system may be configured to manage one or moreconsent receipts for a particular entity. As may be understood from thisfigure, a data subject may access an interaction interface (e.g., viathe web) for interacting with a particular entity (e.g., one or moreentity systems). The interaction interface (e.g., user interface) mayinclude, for example, a suitable website, web form, user interface etc.The interaction interface may be provided by the entity. Using theinteraction interface, a data subject may initiate a transaction withthe entity that requires the data subject to provide valid consent(e.g., because the transaction includes the processing of personal databy the entity). The transaction may include, for example: (1) accessingthe entity's website; (2) signing up for a user account with the entity;(3) signing up for a mailing list with the entity; (4) a free trial signup; (5) product registration; and/or (6) any other suitable transactionthat may result in collection and/or processing personal data, by theentity, about the data subject.

As may be understood from this disclosure, any particular transactionmay record and/or require one or more valid consents from the datasubject. For example, the system may require a particular data subjectto provide consent for each particular type of personal data that willbe collected as part of the transaction. The system may, in variousembodiments, be configured to prompt the data subject to provide validconsent, for example, by: (1) displaying, via the interaction interface,one or more pieces of information regarding the consent (e.g., whatpersonal data will be collected, how it will be used, etc.); and (2)prompt the data subject to provide the consent.

In response to the data subject (e.g., or the entity) initiating thetransaction, the system may be configured to: (1) generate a uniquereceipt key (e.g., unique receipt ID); (2) associate the unique receiptkey with the data subject (e.g., a unique subject identifier), theentity, and the transaction; and (3) electronically store (e.g., incomputer memory) the unique receipt key. The system may further store aunique user ID (e.g., unique subject identifier) associated with thedata subject (e.g., a hashed user ID, a unique user ID provided by thedata subject, unique ID based on a piece of personal data such as ane-mail address, etc.).

In a particular embodiment, the unique consent receipt key is generatedby a third-party consent receipt management system. The system may thenbe configured to associate the unique consent receipt key with theinteraction interface, and further configured to associate the uniqueconsent receipt key with a unique transaction ID generated as a resultof a data subject transaction initiated via the interaction interface.

In particular embodiments, the unique consent receipt key may beassociated with one or more receipt definitions, which may include, forexample: (1) the unique transaction ID; (2) an identity of one or morecontrollers and/or representatives of the entity that is engaging in thetransaction with the data subject (e.g., and contact information for theone or more controllers); (3) one or more links to a privacy policyassociated with the transaction at the time that consent was given; (4)a listing of one or more data types for which consent to process wasprovided (e.g., email, MAC address, name, phone number, browsinghistory, etc.); (5) one or more methods used to collect data for whichconsent to process was provided (e.g., using one or more cookies,receiving the personal data from the data subject directly, etc.); (6) adescription of a service (e.g., a service provided as part of thetransaction such as a free trial, user account, etc.); (7) one or morepurposes of the processing (e.g., for marketing purposes, to facilitatecontact with the data subject, etc.); (8) a jurisdiction (e.g., theEuropean Union, United States, etc.); (9) a legal basis for thecollection of personal data (e.g., consent); (10) a type of consentprovided by the data subject (e.g. unambiguous, explicit, etc.); (11)one or more categories or identities of other entities to whom thepersonal data may be transferred; (12) one or more bases of a transferto a third party entity (e.g., adequacy, binding corporate rules, etc.);(13) a retention period for the personal data (e.g., how long thepersonal data will be stored); (14) a withdrawal mechanism (e.g., a linkto a withdrawal mechanism); (15) a timestamp (e.g., date and time); (16)a unique identifier for the receipt; and/or (17) any other suitableinformation. FIG. 39 depicts an exemplary consent definition summary fora particular transaction (e.g., free trial signup).

In response to receiving valid consent from the data subject, the systemis configured to transmit the unique transaction ID and the uniqueconsent receipt key back to the third-party consent receipt managementsystem for processing and/or storage. In any embodiment describedherein, the system is configured to transmit the transaction ID to adata store associated with one or more entity systems (e.g., for aparticular entity on behalf of whom the third-party consent receiptmanagement system is obtaining and managing validly received consent).In further embodiments, the system is configured to transmit the uniquetransaction ID, the unique consent receipt key, and any other suitableinformation related to the validly given consent to the centralized datarepository system described above for use in determining whether tostore particular data and/or for assigning a unique identifier to aparticular data subject for centralized data repository managementpurposes.

The system may be further configured to transmit a consent receipt tothe data subject which may include, for example: (1) the uniquetransaction ID; (2) the unique consent receipt key; and/or (3) any othersuitable data related to the validly provided consent. In someembodiments, the system is configured to transmit a consent receipt inany suitable format (e.g., JSON, HTML, e-mail, text, cookie, etc.). Inparticular embodiments, the receipt transmitted to the data subject mayinclude a link to a subject rights portal via which the data subjectmay, for example: (1) view one or more provided valid consents; (2)withdraw consent; (3) etc.

Exemplary Data Subject Consent Receipt User Experience

FIGS. 40 and 41 depict exemplary screen displays that a data subject mayencounter when providing consent to the processing of personal data. Asshown in FIG. 40, a data subject (e.g., John Doe) may provide particularpersonal data (e.g., first and last name, email, company, job title,phone number, etc.) when signing up for a free trial with a particularentity via a trial signup interface 4000. As may be understood in lightof this disclosure, the free trial may constitute a transaction betweenthe data subject (e.g., user) and a particular entity providing the freetrial. In various embodiments, the data subject (e.g., user) mayencounter the interface shown in FIG. 40 in response to accessing awebsite associated with the particular entity for the free trial (e.g.,a sign-up page).

In particular embodiments, the interface 4000 is configured to enablethe user (e.g., data subject) to provide the information required tosign up for the free trial. As shown in FIG. 40, the interface furtherincludes a listing of particular things that the data subject isconsenting to (e.g., the processing of first name, last name, workemail, company, job title, and phone number) as well as one or morepurposes for the processing of such data (e.g., marketing information).The interface further includes a link to a Privacy Policy that governsthe use of the information.

In various embodiments, in response to the user (e.g., data subject)submitting the webform shown in FIG. 40, the system is configured togenerate a consent receipt that memorializes the user's provision of theconsent (e.g., by virtue of the user submitting the form). FIG. 41depicts an exemplary consent receipt 4100 in the form of a messagetransmitted to the data subject (e.g., via e-mail). As shown in thisfigure, the consent receipt includes, for example: (1) a receipt number(e.g., a hash, key, or other unique identifier); (2) what informationwas processed as a result of the user's consent (e.g., first and lastname, email, company, job title, phone number, etc.); (3) one or morepurposes of the processing (e.g., marketing information); (4)information regarding withdrawal of consent; (5) a link to withdrawconsent; and (6) a timestamp at which the system received the consent(e.g., a time at which the user submitted the form in FIG. 40). In anyembodiment described herein, the consent receipt transmitted to the usermay include any other suitable information.

FIG. 42 depicts an exemplary log of consent receipts 4200 for aparticular transaction (e.g., the free trial signup described above). Asshown in this figure, the system is configured to maintain a database ofconsent receipts that includes, for example, a timestamp of eachreceipt, a unique key associated with each receipt, a customer IDassociated with each receipt (e.g., the customer's e-mail address), etc.In particular embodiments, the centralized data repository systemdescribed above may be configured to cross-reference the database ofconsent receipts (e.g., or maintain the database) in response toreceiving the indication that a first party system has received, stored,and/or processed personal data (e.g., via the free trial signupinterface) in order to confirm that the data subject has provided validconsent prior to storing the indication of the personal data.

Exemplary Transaction Creation User Experience

FIGS. 43-54 depict exemplary user interfaces via which a user (e.g., acontroller or other individual associated with a particular entity) maycreate a new transaction for which the system is configured to generatea new interaction interface (e.g., interface via which the system isconfigured to elicit and receive consent for the collection and/orprocessing of personal data from a data subject under the newtransaction.

As shown in FIG. 43, the system is configured to display a dashboard ofexisting transactions 4300 that are associated with a particular entity.In the example shown in this figure, the dashboard includes, forexample: (1) a name of each transaction; (2) a status of eachtransaction; (2) one or more data categories collected as part of eachtransaction; (3) a unique subject ID used as part of the transaction(e.g., email, device ID, etc.); (4) a creation date of each transaction;(5) a date of first consent receipt under each transaction; and (6) atotal number of receipts received for each transaction. The dashboardfurther includes a Create New Transaction button, which a user mayselect in order to create a new transaction.

As may be understood in light of this disclosure, in variousembodiments, the centralized data repository system described above maylimit storage of personal data on behalf of a particular entity tospecific personal data for which the particular entity has receivedconsent from particular data subjects. Based on the exemplary dashboardof existing transactions shown in FIG. 43, for example, the system maybe configured to not store any personal data collected, and/or processedother than in response to an indication that the data was collectedthrough the free trial signup or product registration transaction.

FIG. 44 depicts an interface 4400 for creating a new transaction, whicha user may access, for example, by selecting the Create New Transactionbutton shown in FIG. 43. As may be understood from this figure, whencreating a new transaction, the user may enter, via one or more textentry forms, a name of the transaction, a description of thetransaction, a group associated with the transaction, and/or any othersuitable information related to the new transaction.

Continuing to FIG. 45, the system may be configured to prompt the userto select whether the new transaction is based on an existing processingactivity. An existing processing activity may include, for example, anyother suitable transaction or any other activity that involves thecollection and/or processing of personal data. In response to the userselecting that the new transaction is not related to an existingprocessing activity (e.g., as shown in FIG. 45), the system may beconfigured to prompt the user, via one or more additional interfaces, toprovide information regarding the new transaction.

FIGS. 47-54 depict exemplary user interfaces via which the user mayprovide additional information regarding the new transaction. In variousembodiments, the system may be configured to prompt the user to providethe information via free-form text entry, via one or more drop downmenus, by selecting one or more predefined selections, or in anysuitable manner. In some embodiments, the system is configured to promptthe user to provide one or more standardized pieces of informationregarding the new transaction. In any embodiment described herein, thesystem is configured to enable a particular entity (e.g., organization,company, etc.) to customize one or more questions or prompts that thesystem displays to a user creating a new transaction.

As shown in FIG. 46, the system may, for example, prompt the user, viathe user interface, to: (1) describe a process or service that theconsent under the transaction relates to; (2) provide a public URL whereconsent is or will be collected; (3) provide information regarding howconsent is being collected (e.g., via a website, application, device,paper form, etc.); (4) provide information regarding one or more dataelements that will be processed based on the consent provided by thedata subject (e.g., what particular personal data will be collected);and (5) provide information regarding what data elements are processedby one or more background checks (e.g., credit check and/or criminalhistory).

Continuing to FIG. 47, the system may be configured to prompt the userto provide data related to, for example: (1) one or more elements thatwill be used to uniquely identify a data subject; (2) a purpose forseeking consent; (3) what type of consent is sought (e.g., unambiguous,explicit, not sure, etc.); (4) who is the data controller in charge ofthe processing of the personal data (e.g., the legal entityresponsible); (5) a contact address (e.g., for the data controller; (6)etc.

As shown in FIG. 48, the system may be further configured to prompt theuser to provide data regarding, for example: (1) who the contact personis for the transaction (e.g., a job title, name, etc. of the contactperson); (2) a contact email (e.g., an email address that a data subjectcan contact to get more information about the transaction, consent,etc.); (3) a contact telephone number (e.g., a telephone number that adata subject can contact to get more information about the transaction,consent, etc.); (4) an applicable jurisdiction for the processing (e.g.,European Union, United States, Other, etc.), which may include one ormore jurisdictions; (5) a URL of a privacy policy associated with thetransaction; (6) etc.

Next, as shown in FIG. 49, the system may be further configured toprompt the user to provide data regarding: (1) whether the personal datawill be shared with one or more third parties; (2) a name of the one ormore third parties; (3) whether the processing of the personal data willinvolve a transfer of the personal data outside of the originaljurisdiction; (4) a listing of one or more destination countries,regions, or other jurisdictions that will be involved in anyinternational transfer; (5) a process for a data subject to withdrawconsent; (6) a URL for the withdrawal mechanism; (7) etc. FIG. 50depicts a user interface that includes additional data prompts for theuser to respond to regarding the new transaction. As shown in FIG. 50,the system may be further configured to prompt the user to provide dataregarding, for example: (1) what the retention period is for thepersonal data (e.g., how long the personal data will be stored inidentifiable form, a period before anonymization of the personal data,etc.); and/or (2) a life span of the consent (e.g., a period of timeduring which the consent is assumed to be valid).

FIG. 51 shows an exemplary user interface for selecting a processingactivity in response to the user indicating that the new transaction isbased on an existing processing activity. The user may, for example, usea drop-down menu to select a suitable existing processing activity. Inparticular embodiments, the system is configured to populate thedrop-down menu with one or more processing activities from a data modelassociated with the processing activity. The system may then beconfigured to substantially automatically populate one or more responsesto the questions described above based at least in part on the datamodel (e.g., automatically include particular data elements collected aspart of the processing activity, etc.).

In particular embodiments, the system is further configured to enable acontroller (e.g., or other user on behalf of the entity) to search forone or more consent receipts received for a particular data subject(e.g., via a unique subject identifier). FIG. 52 depicts a search for aunique subject identifier that includes an e-mail address. As shown inthis figure, the unique subject identifier (e.g., john.doe@gmail.com)has one associated consent receipt having a receipt number, a receiptdate and time, and a withdrawal date. FIG. 53 depicts an additionalexemplary search results page indicating one or more results for consentreceipts associated with the unique subject identifier ofjohn.doe@gmail.com. As shown in this figure, the system may beconfigured to display a process name (e.g., transaction name), receiptnumber, consent date, status, withdrawal date, and other suitableinformation for one or more consent receipts associated with thesearched for unique subject identifier.

As may be understood in light of this disclosure, in response to a usercreating a new transaction, the system may be configured to generate aweb form, web page, piece of computer code, etc. for the collection ofconsent by a data subject as part of the new transaction. FIG. 54depicts an exemplary dashboard of consent receipt managementimplementation code which the system may automatically generate for theimplementation of a consent receipt management system for a particulartransaction. As shown in this figure, the system displays particularcomputer code (e.g., in one or more different programming language) thatthe system has generated. A user may place the generated code on awebpage or other location that the user desires to collect consent.

Exemplary Consent Receipt Management System Architecture

FIG. 55 is a block diagram of a Consent Receipt Management System 5500according to a particular embodiment. In some embodiments, the ConsentReceipt Management System 5500 is configured to interface with at leasta portion of each respective organization's Privacy Compliance System inorder generate, capture, and maintain a record of one or more consentsto process, collect, and or store personal data from one or more datasubjects.

As may be understood from FIG. 55, the Consent Receipt Management System5500 includes one or more computer networks 115, a Consent ReceiptManagement Server 5510, a Consent Receipt Capture Server 5520 (e.g.,which may be configured to run one or more virtual browsers 5525 asdescribed herein), One or More Consent Web Form Hosting Servers 5530,one or more databases 140, and one or more remote computing devices 5550(e.g., a desktop computer, laptop computer, tablet computer, etc.). Inparticular embodiments, the one or more computer networks 115 facilitatecommunication between the Consent Receipt Management Server 5510, aConsent Receipt Capture Server 5520, One or More Consent Web FormHosting Servers 5530, one or more databases 140, and one or more remotecomputing devices 5550.

The one or more computer networks 115 may include any of a variety oftypes of wired or wireless computer networks such as the Internet, aprivate intranet, a public switch telephone network (PSTN), or any othertype of network. The communication link between Consent Receipt CaptureServer 5520 and Database 140 may be, for example, implemented via aLocal Area Network (LAN) or via the Internet.

Exemplary Consent Receipt Management System Platform

Various embodiments of a Consent Receipt Management System 5500 4500 maybe implemented in the context of any suitable system (e.g., a privacycompliance system). For example, the Consent Receipt Management System5500 may be implemented to facilitate receipt and maintenance of one ormore valid consents provided by one or more data subjects for theprocessing and/or at least temporary storage of personal data associatedwith the data subjects. In particular embodiments, the system mayimplement one or more modules in order to at least partially ensurecompliance with one or more regulations (e.g., legal requirements)related to the collection and/or storage of personal data. Variousaspects of the system's functionality may be executed by certain systemmodules, including a Consent Receipt Management Module 5600, a ConsentExpiration and Re-Triggering Module 5700, and a Consent Validity ScoringModule 5900. These modules are discussed in greater detail below.

Although the system may be configured to execute the functions describedin the modules as a series of steps, it should be understood in light ofthis disclosure that various embodiments of the Consent ReceiptManagement Module 5600, Consent Expiration and Re-Triggering Module5700, and Consent Validity Scoring Module 5900 described herein mayperform the steps described below in an order other than in which theyare presented. In still any embodiment described herein, the ConsentReceipt Management Module 5600, Consent Expiration and Re-TriggeringModule 5700, and Consent Validity Scoring Module 5900 may omit certainsteps described below. In any embodiment described herein, the ConsentReceipt Management Module 5600, Consent Expiration and Re-TriggeringModule 5700, and Consent Validity Scoring Module 5900 may perform stepsin addition to those described (e.g., such as one or more stepsdescribed with respect to one or more other modules, etc.).

Consent Receipt Generation

In various embodiments, a consent receipt management system isconfigured to generate a consent receipt for a data subject that linksto (e.g., in computer memory) metadata identifying a particular purposeof the collection and/or processing of personal data that the datasubject consented to, a capture point of the consent (e.g., a copy ofthe web form or other mechanism through which the data subject providedconsent, and other data associated with one or more ways in which thedata subject granted consent.

The system may, for example, be configured to track data on behalf of anentity that collects and/or processes persona data related to: (1) whoconsented to the processing or collection of personal data (e.g., thedata subject themselves or a person legally entitled to consent on theirbehalf such as a parent, guardian, etc.); (2) when the consent was given(e.g., a date and time); (3) what information was provided to theconsenter at the time of consent (e.g., a privacy policy, what personaldata would be collected following the provision of the consent, for whatpurpose that personal data would be collected, etc.); (4) how consentwas received (e.g., one or more copies of a data capture form, web form,etc. via which consent was provided by the consenter); (5) when consentwas withdrawn (e.g., a date and time of consent withdrawal if theconsenter withdraws consent); and/or (6) any other suitable data relatedto receipt or withdrawal of consent.

Using an interaction interface, a data subject may initiate atransaction with the entity that requires the data subject to providevalid consent (e.g., because the transaction includes the processing ofpersonal data by the entity). The transaction may include, for example:(1) accessing the entity's website (e.g., which may utilize one or morecookies and/or other tracking technologies to monitor the data subject'sactivity while accessing the website or other websites; enable certainfunctionality on one or more pages of the entity's website, such aslocation services; etc.); (2) signing up for a user account with theentity; (3) signing up for a mailing list with the entity; (4) a freetrial sign up; (5) product registration; and/or (6) any other suitabletransaction that may result in collection and/or processing of personaldata, by the entity, about the data subject.

As may be understood from this disclosure, any particular transactionmay record and/or require one or more valid consents from the datasubject. For example, the system may require a particular data subjectto provide consent for each particular type of personal data that willbe collected as part of the transaction. The system may, in variousembodiments, be configured to prompt the data subject to provide validconsent, for example, by: (1) displaying, via the interaction interface,one or more pieces of information regarding the consent (e.g., whatpersonal data will be collected, how it will be used, etc.); and (2)prompt the data subject to provide the consent.

In response to the data subject (e.g., or the entity) initiating thetransaction, the system may be configured to: (1) generate a uniquereceipt key (e.g., unique receipt ID); (2) associate the unique receiptkey with the data subject (e.g., via a unique subject identifier), theentity, and the transaction; and (3) electronically store (e.g., incomputer memory) the unique receipt key. The system may further store aunique user ID (e.g., unique subject identifier) associated with thedata subject (e.g., a hashed user ID, a unique user ID provided by thedata subject, unique ID based on a piece of personal data such as ane-mail address, etc.). In any embodiment described herein, the systemmay be configured to store computer code associated with the capture ofthe consent by the system. The system may, for example, store computercode associated with a web form or other consent capture mechanism. Inany embodiment described herein, the system is configured to capture oneor more images of one or more webpages via which a data subject provides(e.g., provided) consent (e.g., substantially at the time at which thedata subject provided consent). This may, for example, enable an entityor other organization to demonstrate one or more conditions under whichconsent was received for a particular data subject in order to complywith one or more regulations related to the securing of consent.

In a particular embodiment, the system is configured to: (1) use avirtual web browser to access a URL via which a data subject providedconsent for a particular processing activity or other transaction; (2)capture one or more images of one or more websites at the URL, the oneor more images containing one or more web forms or other portions of theone or more web pages via which the data subject provided one or moreinputs that demonstrated the data subject's consent; and store the oneor more images in association with metadata associated with one or moreconsent receipts related to the received consent. In some embodiments,the system may be configured to: (1) scan, via the virtual web browser,a particular website and/or URL; (2) identify a web form at theparticular website and/or URL; and (3) capture one or more images (e.g.,screenshots) of the web form (e.g., in an unfilled-out state). In someembodiments, the system is configured to use a virtual web browser thatcorresponds to a web browser via which the user completed the web form.For example, the system may be configured to identify a particular webbrowser utilized by the data subject and initiate the virtual browsingsession using the identified web browser.

FIG. 55 depicts an exemplary Consent Receipt Management Module 5500 thatincludes steps that the system may execute in order to generate aconsent receipt. As may be understood from FIG. 55, the system may beconfigured to: (1) provide a user interface for initiating a transactionbetween an entity and a data subject (e.g., such as a web form via whichthe data subject may authorize or consent to the processing, collection,or storage of personal data associated with the transaction); (2)receive a request to initiate a transaction between the entity and thedata subject (e.g., from a computing device associated with the datasubject via a web form located at a particular URL, on a particularwebpage, etc.); (3) in response to receiving the request, generating, bya third party consent receipt management system, a unique consentreceipt key; (4) in response to receiving the request, initiating avirtual browsing session on a second computing device (e.g., a secondcomputing device associated with the third party consent receiptmanagement system); (5) using the virtual browser to access theparticular URL or particular webpage that hosts the web form; (6)capturing, via the virtual browser, one or more images of the web form,the URL, and/or the particular webpage; (7) store a unique subjectidentifier associated with the data subject, the unique consent receiptkey, a unique transaction identifier associated with the transaction,and the one or more images in computer memory; and (8) electronicallyassociating the unique subject identifier, the unique consent receiptkey, the unique transaction identifier, and the one or more images.

FIG. 40 depicts an exemplary screen display that a data subject mayencounter when providing consent to the processing of personal data. Asshown in FIG. 40, a data subject (e.g., John Doe) may provide particularpersonal data (e.g., first and last name, email, company, job title,phone number, etc.) when signing up for a free trial with a particularentity. As may be understood in light of this disclosure, the free trialmay constitute a transaction between the data subject (e.g., user) and aparticular entity providing the free trial. In various embodiments, thedata subject (e.g., user) may encounter the interface shown in FIG. 40in response to accessing a website associated with the particular entityfor the free trial (e.g., a sign-up page).

In particular embodiments, the interface is configured to enable theuser (e.g., data subject) to provide the information required to sign upfor the free trial. As shown in FIG. 40, the interface further includesa listing of particular things that the data subject is consenting to(e.g., the processing of first name, last name, work email, company, jobtitle, and phone number) as well as one or more purposes for theprocessing of such data (e.g., marketing information). The interfacefurther includes a link to a Privacy Policy that governs the use of theinformation.

In various embodiments, in response to the user (e.g., data subject)submitting the webform shown in FIG. 40, the system is configured togenerate a consent receipt that memorializes the user's provision of theconsent (e.g., by virtue of the user submitting the form). FIG. 40depicts an uncompleted version of the web form from FIG. 40 that thesystem may capture via a virtual browsing session described herein andstore in association with the consent receipt. FIG. 41 depicts anexemplary consent receipt in the form of a message transmitted to thedata subject (e.g., via e-mail). As shown in this figure, the consentreceipt includes, for example: (1) a receipt number (e.g., a hash, key,or other unique identifier); (2) what information was processed as aresult of the user's consent (e.g., first and last name, email, company,job title, phone number, etc.); (3) one or more purposes of theprocessing (e.g., marketing information); (4) information regardingwithdrawal of consent; (5) a link to withdraw consent; and (6) atimestamp at which the system received the consent (e.g., a time atwhich the user submitted the form in FIG. 2). In any embodimentdescribed herein, the consent receipt transmitted to the user mayinclude any other suitable information (e.g., such as a link to anunfilled out version of the web form via which the user providedconsent, etc.)

In particular embodiments, the system is configured to generate a codeassociated with a particular web form. The system may then associate thecode with a particular website, mobile application, or other locationthat hosts the web form.

In any embodiment described herein, the system is configured to captureone or more images (e.g., and/or one or more copies) of one or moreprivacy policies and/or privacy notices associated with the transactionor processing activity. This may include, for example, one or moreprivacy policies and/or privacy notices that dictate one or more termsunder which the data subject provided consent (e.g., consent to havepersonal data associated with the data subject processed, collected,and/or stored). The system may be further configured to store andassociate the captured one or more privacy policies and/or privacynotices with one or more of the unique subject identifiers, the uniqueconsent receipt key, the unique transaction identifier, etc.

In various embodiments, the system is configured to generate a web formfor use by an entity to capture consent from one or more data subjects.In any embodiment described herein, the system is configured tointegrate with an existing web form. The system may, for example, beconfigured to record each particular selection and/or text entry by thedata subject via the web form and capture (e.g., via the virtualbrowsing session described above) one or more images (e.g., screenshots)which may demonstrate what the web form looked like at the time theconsent was provided (e.g., in an unfilled out state).

As may be understood in light of this disclosure, in response to a usercreating a new transaction on behalf of an entity, the system may beconfigured to generate a web form, web page, piece of computer code,etc. for the collection of consent by a data subject as part of the newtransaction. FIG. 54 depicts an exemplary dashboard of consent receiptmanagement implementation code which the system may automaticallygenerate for the implementation of a consent receipt management systemfor a particular transaction. As shown in this figure, the systemdisplays particular computer code (e.g., in one or more differentprogramming language) that the system has generated. A user may placethe generated code on a webpage, within a mobile application, or otherlocation that the user desires to collect consent.

In some embodiments, the system is configured to capture and store theunderlying code for a particular web form (e.g., HTML, or other suitablecomputer code), which may, for example, be used to demonstrate how theconsent from the data subject was captured at the time of the capture.In some embodiments, the system may be configured to capture theunderlying code via the virtual browsing session described above.

In particular embodiments, the system is configured to enable an entityto track one or more consent provisions or revocations received via oneor more venues other than via a computing device. For example, a datasubject may provide or revoke consent via: (1) a phone call; (2) viapaper (e.g., paper mailing); and/or (3) any other suitable avenue. Thesystem may, for example, provide an interface via which a customersupport representation can log a phone call from a data subject (e.g., arecording of the phone call) and generate a receipt indicating that thecall occurred, what was requested on the call, whether the request wasfulfilled, and a recording of the call. Similarly, the system may beconfigured to provide an interface to scan or capture one or more imagesof one or more consents provided or revoked via mail (e.g., snail mail).

Consent Receipts—Automatic Expiration and Triggering of ConsentRecapture

In particular embodiments, the consent receipt management system isconfigured to: (1) automatically cause a prior, validly received consentto expire (e.g., in response to a triggering event); and (2) in responseto causing the previously received consent to expire, automaticallytrigger a recapture of consent. In particular embodiments, the systemmay, for example, be configured to cause a prior, validly receivedconsent to expire in response to one or more triggering events such as:(1) a passage of a particular amount of time since the system receivedthe valid consent (e.g., a particular number of days, weeks, months,etc.); (2) one or more changes to a purpose of the data collection forwhich consent was received (e.g., or one or more other changes to one ormore conditions under which the consent was received; (3) one or morechanges to a privacy policy associated with the consent; (3) one or morechanges to one or more rules (e.g., laws, regulations, etc.) that governthe collection or demonstration of validly received consent; and/or (4)any other suitable triggering event or combination of events. Inparticular embodiments, such as any embodiment described herein, thesystem may be configured to link a particular consent received from adata subject to a particular version of a privacy policy, to aparticular version of a web form through which the data subject providedthe consent, etc. The system may then be configured to detect one ormore changes to the underlying privacy policy, consent receiptmethodology, etc., and, in response, automatically expire one or moreconsents provided by one or more data subjects under a previous versionof the privacy policy or consent capture form.

In various embodiments, the system may be configured to substantiallyautomatically expire a particular data subject's prior provided consentin response to a change in location of the data subject. The system may,for example, determine that a data subject is currently located in ajurisdiction, country, or other geographic location other than thelocation in which the data subject provided consent for the collectionand/or processing of their personal data. The system may be configuredto determine that the data subject is in a new location based at leastin part on, for example, a geolocation (e.g., GPS location) of a mobilecomputing device associated with the data subject, an IP address of oneor more computing devices associated with the data subject, etc.). Asmay be understood in light of this disclosure, one or more differentcountries, jurisdictions, etc. may impose different rules, regulations,etc. related to the collection, storage, and processing of personaldata. As such, in response to a user moving to a new location (e.g., orin response to a user temporarily being present in a new location), thesystem may be configured to trigger a recapture of consent based on oneor more differences between one or more rules or regulations in the newlocation and the original location from which the data subject providedconsent. In some embodiments, the system may substantially automaticallycompare the one or more rules and/or regulations of the new and originallocations to determine whether a recapture of consent is necessary.

In particular embodiments, in response to the automatic expiration ofconsent, the system may be configured to automatically trigger arecapture of consent (e.g., based on the triggering event). The systemmay, for example, prompt the data subject to re-provide consent using,for example: (1) an updated version of the relevant privacy policy; (2)an updated web form that provides one or more new purposes for thecollection of particular personal data; (3) one or more web forms orother consent capture methodologies that comply with one or more changesto one or more legal, industry, or other regulations; and/or (4) etc.

FIG. 57 depicts an exemplary Consent Expiration and Re-Triggering Module5700 according to a particular embodiment. In various embodiments, whenexecuting the Consent Expiration and Re-Triggering Module 5700, thesystem is configured to, beginning at Step S710, by determining that atriggering event has occurred. In various embodiments, the triggeringevent may include nay suitable triggering event such as, for example:(1) passage of a particular amount of time since a valid consent wasreceived; (2) determination that a data subject for which the system haspreviously received consent is now located in a new jurisdiction,country, geographic location, etc.; (3) a change to one or more uses ofdata for which the data subject provided consent for the collectionand/or processing; (4) a change to one or more privacy policies; and/or(5) any other suitable triggering event related to one or more consentsreceived by the system.

Continuing to Step S720, the system is configured to cause an expirationof at least one validly received consent in response to determining thatthe triggering event has occurred. In response to causing the expirationof the at least one consent, the system may be configured to ceaseprocessing, collecting, and/or storing personal data associated with theprior provided consent (e.g., that has now expired). The system maythen, at Step S730, in response to causing the expiration of the atleast one validly received consent, automatically trigger a recapture ofthe at least one expired consent.

Consent Preference Modification Capture Systems

In particular embodiments, the consent receipt management system isconfigured to provide a centralized repository of consent receiptpreferences for a plurality of data subjects. In various embodiments,the system is configured to provide an interface to the plurality ofdata subjects for modifying consent preferences and capture consentpreference changes. The system may provide the ability to track theconsent status of pending and confirmed consents. In any embodimentdescribed herein, the system may provide a centralized repository ofconsent receipts that a third-party system may reference when taking oneor more actions related to a processing activity. For example, aparticular entity may provide a newsletter that one or more datasubjects have consented to receiving. Each of the one or more datasubjects may have different preferences related to how frequently theywould like to receive the newsletter, etc. In particular embodiments,the consent receipt management system may receive a request from athird-party system to transmit the newsletter to the plurality of datasubjects. The system may then cross-reference an updated consentdatabase to determine which of the data subjects have a current consentto receive the newsletter, and whether transmitting the newsletter wouldconflict with any of those data subjects' particular frequencypreferences. The system may then be configured to transmit thenewsletter to the appropriate identified data subjects.

In particular embodiments, the system may be configured to identifyparticular consents requiring a double opt-in (e.g., an initial consentfollowed by a confirmatory consent in respond to generation of aninitial consent receipt in order for consent to be valid). In particularembodiments, the system may track consents with a “half opt-in” consentstatus and take one or more steps to complete the consent (e.g., one ormore steps described below with respect to consent conversionanalytics).

The system may also, in particular embodiments, proactively modifysubscriptions or other preferences for users in similar demographicsbased on machine learning of other users in that demographic opting tomake such modifications. For example, the system may be configured tomodify a user's preferences related to a subscription frequency for anewsletter or make other modifications in response to determining thatone or more similarly situated data subjects (e.g., subjects of similarage, gender, occupation, etc.) have mad such modifications. In variousembodiments, the system may be configured to increase a number of datasubjects that maintain consent to particular processing activities whileensuring that the entity undertaking the processing activities complieswith one or more regulations that apply to the processing activities.

Consent Conversion Analytics

In particular embodiments, a consent receipt management system isconfigured to track and analyze one or more attributes of a userinterface via which data subjects are requested to provide consent(e.g., consent to process, collect, and/or store personal data) in orderto determine which of the one or more attributes are more likely toresult in a successful receipt of consent from a data subject. Forexample, the system may be configured to analyze one or more instancesin which one or more data subjects provided or did not provide consentin order to identify particular attributes and/or factors that mayincrease a likelihood of a data subject providing consent. The one ormore attributes may include, for example: (1) a time of day at whichparticular data subjects provided/did not provide consent; (2) a lengthof an e-mail requesting consent in response to which particular datasubjects provided/did not provide consent; (3) a number of e-mailsrequesting consent in a particular time period sent to particular datasubjects in response to at least one of which particular data subjectsprovided/did not provide consent; (4) how purpose-specific a particularemail requesting consent was; (5) whether an e-mail requesting consentprovided one or more opt-down options (e.g., one or more options toconsent to receive a newsletter less frequently); (5) whether the e-mailrequesting consent included an offer; (6) how compelling the offer was;(7) etc. The system may then aggregate these analyzed attributes andwhether specific attributes increased or decreased a likelihood that aparticular data subject may provide consent and use the aggregatedanalysis to automatically design a user interface, e-mail message, etc.that is configured to maximize consent receipt conversion based on theanalytics.

In particular embodiments, the system may further be configured togenerate a customized interface or message requesting consent for aparticular data subject based at least in part on an analysis ofsimilarly situated data subjects that provided consent based onparticular attributes of an e-mail message or interface via which theconsent was provided. For example, the system may identify one or moresimilarly situated data subjects based at least in part on: (1) age; (2)gender; (3) occupation; (4) income level; (5) interests, etc. Inparticular embodiments, a male between the ages of 18-25 may, forexample, respond to a request for consent with a first set of attributesmore favorably than a woman between the ages of 45 and 50 (e.g., who mayrespond more favorably to a second set of attributes).

The system may be configured to analyze a complete consent journey(e.g., from initial consent, to consent confirmation in cases where adouble opt-in is required to validly receive consent). In particularembodiments, the system is configured to design interfaces particularlyto capture the second step of a double opt-in consent or to recaptureconsent in response to a change in conditions under which consent wasinitially provided.

In particular embodiments, the system may be configured to use theanalytics described herein to determine a particular layout,interaction, time of day, number of e-mails, etc. cause the highestconversion rate across a plurality of data subjects (e.g., across aplurality of similarly situated data subjects of a similar demographic).

FIG. 58 depicts an exemplary consent conversion analysis interface. Asmay be understood from this figure, the system may be configured totrack, for example: (1) total unique visitors to a particular website(e.g., to which the system may attempt to obtain consent for particulardata processing); (2) overall opt-in percentage of consent; (3) opt-inpercent by actions; (4) opt-out percentage by actions, etc.

Consent Validity Scoring Systems

In particular embodiments, a consent receipt management system mayinclude one or more consent validity scoring systems. In variousembodiments, a consent validity scoring system may be configured todetect a likelihood that a user is correctly consenting via a web form.The system may be configured to determine such a likelihood based atleast in part on one or more data subject behaviors while the datasubject is completing the web form in order to provide consent. Invarious embodiments, the system is configured to monitor the datasubject behavior based on, for example: (1) mouse speed; (2) mousehovering; (3) mouse position; (4) keyboard inputs; (5) an amount of timespent completing the web form; and/or (5) any other suitable behavior orattribute. The system may be further configured to calculate a consentvalidity score for each generated consent receipt based at least in parton an analysis of the data subject's behavior (e.g., inputs, lack ofinputs, time spent completing the consent form, etc.).

In particular embodiments, the system is configured to monitor the datasubject's (e.g., the user's) system inputs while the data subject iscompeting a particular web form. In particular embodiments activelymonitoring the user's system inputs may include, for example,monitoring, recording, tracking, and/or otherwise taking account of theuser's system inputs. These system inputs may include, for example: (1)one or more mouse inputs; (2) one or more keyboard (e.g., text) inputs;(3) one or more touch inputs; and/or (4) any other suitable inputs(e.g., such as one or more vocal inputs, etc.). In any embodimentdescribed herein, the system is configured to monitor one or morebiometric indicators associated with the user such as, for example,heart rate, pupil dilation, perspiration rate, etc.

In particular embodiments, the system is configured to monitor a user'sinputs, for example, by substantially automatically tracking a locationof the user's mouse pointer with respect to one or more selectableobjects on a display screen of a computing device. In particularembodiments, the one or more selectable objects are one or moreselectable objects (e.g., indicia) that make up part of the web form. Instill any embodiment described herein, the system is configured tomonitor a user's selection of any of the one or more selectable objects,which may include, for example, an initial selection of one or moreselectable objects that the user subsequently changes to selection of adifferent one of the one or more selectable objects.

In any embodiment described herein, the system may be configured tomonitor one or more keyboard inputs (e.g., text inputs) by the user thatmay include, for example, one or more keyboard inputs that the userenters or one or more keyboard inputs that the user enters but deleteswithout submitting. The user may, for example, initially begin typing afirst response, but delete the first response and enter a secondresponse that the user ultimately submits. In various embodiments of thesystem described herein, the system is configured to monitor theun-submitted first response in addition to the submitted secondresponse.

In still any embodiment described herein, the system is configured tomonitor a user's lack of input. For example, a user may mouse over aparticular input indicium (e.g., a selection from a drop-down menu, aradio button or other selectable indicia) without selecting theselection or indicia. In particular embodiments, the system isconfigured to monitor such inputs. As may be understood in light of thisdisclosure, a user that mouses over a particular selection and lingersover the selection without actually selecting it may, for example, bedemonstrating an uncertainty regarding the consent the user isproviding.

In any embodiment described herein, the system is configured to monitorany other suitable input by the user. In various embodiments, this mayinclude, for example: (1) monitoring one or more changes to an input bya user; (2) monitoring one or more inputs that the user later removes ordeletes; (3) monitoring an amount of time that the user spends providinga particular input; and/or (4) monitoring or otherwise tracking anyother suitable information.

In various embodiments, the system is further configured to determinewhether a user has accessed and/or actually scrolled through a privacypolicy associated with a particular transaction. The system may furtherdetermine whether a user has opened an e-mail that includes a summary ofthe consent provided by the user after submission of the web form. Thesystem may then be configured to use any suitable information related tothe completion of the web form or other user activity to calculate aconsent validity score. In various embodiments, the consent validityscore may indicate, for example: (1) an ease at which the user was ableto complete a particular consent form; (2) an indication that aparticular consent may or may not have been freely given; (3) etc. Inparticular embodiments, the system may be configured to trigger arecapture of consent in response to calculating a consent validity scorefor a particular consent that is below a particular amount. In otherembodiment, the system may be configured to confirm a particular user'sconsent depending on a calculated validity score for the consent.

FIG. 59 depicts an exemplary Consent Validity Scoring Module 5900. Asmay be understood from FIG. 59, in various embodiments, when executingthe Consent Validity Scoring Module 5900, the system begins at StepS910, by identifying and analyzing one or more data subject behaviorswhile the data subject is providing consent for particular dataprocessing. IN various embodiments, the one or more data subjectbehaviors may include any suitable data subject behavior describedherein. Continuing to Step S920, the system is configured to determine avalidity score for the provided consent based at least in part on theanalysis at Step S910. The system may then be configured to optionallytrigger a recapture of consent based on the determined validity score.The system may, for example, be configured to capture a recapture ofconsent in response to determining that that the validity score is belowa predetermined level.

Consent Conversion Optimization Systems

In particular embodiments, any entity (e.g., organization, company,etc.) that collects, stores, processes, etc. personal data may requireone or more of: (1) consent from a data subject from whom the personaldata is collected and/or processed; and/or (2) a lawful basis for thecollection and/or processing of the personal data. In variousembodiments, the entity may be required to, for example: (1) demonstratethat a data subject has freely given specific, informed, and unambiguousindication of the data subject's agreement to the processing of his orher personal data (e.g., in the form of a statement or clear affirmativeaction); (2) demonstrate that the entity received consent from a datasubject in a manner clearly distinguishable from other matters (e.g., inan intelligible and easily accessible form, using clear and plainlanguage, etc.); (3) enable a data subject to withdraw consent as easilyas the data subject can give consent; (4) separate a data subject'sconsent from performance under any contract unless such processing isnecessary for performance under the contract; etc.

In particular, when storing or retrieving information from an end user'sdevice, an entity may be required to receive consent from the end userfor such storage and retrieval. Web cookies are a common technology thatmay be directly impacted by the consent requirements discussed herein.Accordingly, an entity that use cookies (e.g., on one or more webpages,such as on one or more webpages that make up a website or series ofwebsites) may be required to use one or more banners, pop-ups or otheruser interfaces on the website (e.g., or a particular webpage of thewebsite) in order to capture consent from end-users to store andretrieve cookie data. In particular, an entity may require consentbefore storing one or more cookies on a user's device and/or trackingthe user via the one or more cookies. In various embodiments, anindividual's consent to an entity's use of cookies may require, forexample, an explicit affirmative action by the individual (e.g.,continued browsing on a webpage and/or series of webpages followingdisplay of a cookie notice, clicking an affirmative consent to the useof cookies via a suitable interface, scrolling a webpage beyond aparticular point, or undertaking any other suitable activities thatrequires the individual (e.g., user) to actively proceed with use of thepage in order to demonstrate consent (e.g., explicit and/or impliedconsent) to the use of cookies. In various embodiments, the system maybe further configured to optimize a consent interface for, for example,one or more software applications (e.g., one or more mobileapplications) or any other suitable application that may require a userto provide consent via any suitable computing device.

The consent required to store and retrieve cookie data may, for example,require a clear affirmative act establishing a freely given, specific,informed and unambiguous indication of a data subject's agreement to theprocessing of personal data. This may include, for example: (1) tickinga box when visiting an internet website; (2) choosing technical settingsfor information security services (e.g., via a suitable user interface);(3) performing a scrolling action; (4) clicking on one or more internallinks of a webpage; and/or (5) or any other suitable statement orconduct which clearly indicates in this context the data subject'sacceptance of the proposed processing of their personal data.

In various embodiments, pre-ticked boxes (or other preselected options)or inactivity may not be sufficient to demonstrate freely given consent.For example, an entity may be unable to rely on implied consent (e.g.,“by visiting this website, you accept cookies”). Without a genuine andfree choice by data subjects and/or other end users, an entity may beunable to demonstrate valid consent (e.g., and therefore unable toutilize cookies in association with such data subjects and/or endusers).

A particular entity may use cookies for any number of suitable reasons.For example, an entity may utilize: (1) one or more functionalitycookies (which may, for example, enhance the functionality of one ormore webpages or a website by storing user preferences such as theuser's location for a weather or news website); (2) one or moreperformance cookies (which may, for example, help to improve performanceof the website on the user's device to provide a better userexperience); (3) one or more targeting cookies (which may, for example,be used by advertising partners to build a profile of interests for auser in order to show relevant advertisements through the website; (4)etc. Cookies may also be used for any other suitable reason such as, forexample: (1) to measure and improve site quality through analysis ofvisitor behavior (e.g., through ‘analytics’); (2) to personalize pagesand remember visitor preferences; (3) to manage shopping carts in onlinestores; (4) to track people across websites and deliver targetedadvertising; (5) etc.

Under various regulations, an entity may not be required to obtainconsent to use every type of cookie utilized by a particular website.For example, strictly necessary cookies, which may include cookies thatare necessary for a website to function, may not require consent. Anexample of strictly necessary cookies may include, for example, sessioncookies. Session cookies may include cookies that are strictly requiredfor website functionality and don't track user activity once the browserwindow is closed. Examples of session cookies include: (1) facetedsearch filter cookies; (2) user authentication cookies; (3) cookies thatenable shopping cart functionality; (4) cookies used to enable playbackof multimedia content; (5) etc.

Cookies which may trigger a requirement for obtaining consent mayinclude cookies such as persistent cookies. Persistent cookies mayinclude, for example, cookies used to track user behavior even after theuse has moved on from a website or closed a browser window.

In order to comply with particular regulations, an entity may berequired to: (1) present visitors with information about the cookies awebsite uses and the purpose of the cookies (e.g., any suitable purposedescribed herein or other suitable purpose); (2) obtain consent to usethose cookies (e.g., obtain separate consent to use each particular typeof cookies used by the website); and (3) provide a mechanism forvisitors to withdraw consent (e.g., that is as straightforward as themechanism through which the visitors initially provided consent). In anyembodiment described herein, an entity may only need to receive validconsent from any particular visitor a single time (e.g., returningvisitors may not be required to provide consent on subsequent visits tothe site). In particular embodiments, although they may not requireexplicit consent to use, an entity may be required to notify a visitorof any strictly necessary cookies used by a website.

Because entities may desire to maximize a number of end users and otherdata subjects that provide this valid consent (e.g., for each type ofcookie for which consent may be required), it may be beneficial toprovide a user interface through which the users are more likely toprovide such consent. By receiving consent from a high number of users,the entity may, for example: (1) receive higher revenue from advertisingpartners; (2) receive more traffic to the website because users of thewebsite may enjoy a better experience while visiting the website; etc.In particular, certain webpage functionality may require the use ofcookies in order for a webpage to fully implement the functionality. Forexample, a national restaurant chain may rely on cookies to identify auser's location in order to direct an order placed via the chain'swebpage to the appropriate local restaurant (e.g., the restaurant thatis located most proximate to the webpage user). A user that is accessingthe restaurant's webpage that has not provided the proper consent to thewebpage to utilize the user's location data may become frustrated by theexperience because some of the webpage features may appear broken. Sucha user may, for example, ultimately exit the webpage, visit a webpage ofa competing restaurant, etc. As such, entities may particular desire toincrease a number of webpage visitors that ultimately provide thedesired consent level so that the visitors to the webpage/website canenjoy all of the intended features of the webpage/website as designed.

In particular embodiments, a consent conversion optimization system isconfigured to test two or more test consent interfaces against oneanother to determine which of the two or more consent interfaces resultsin a higher conversion percentage (e.g., to determine which of the twoor more interfaces lead to a higher number of end users and/or datasubjects providing a requested level of consent for the creation,storage and use or cookies by a particular website). The system may, forexample, analyze end user interaction with each particular test consentinterface to determine which of the two or more user interfaces: (1)result in a higher incidence of a desired level of provided consent; (2)are easier to use by the end users and/or data subjects (e.g., take lesstime to complete, require a fewer number of clicks, etc.); (3) etc.

The system may then be configured to automatically select frombetween/among the two or more test interfaces and use the selectedinterface for future visitors of the website.

In particular embodiments, the system is configured to test the two ormore test consent interfaces against one another by: (1) presenting afirst test interface of the two or more test consent interfaces to afirst portion of visitors to a website/webpage; (2) collecting firstconsent data from the first portion of visitors based on the first testinterface; (3) presenting a second test interface of the two or moretest consent interfaces to a second portion of visitors to thewebsite/webpage; (4) collecting second consent data from the secondportion of visitors based on the second test interface; (5) analyzingand comparing the first consent data and second consent data todetermine which of the first and second test interface results in ahigher incidence of desired consent; and (6) selecting between the firstand second test interface based on the analysis.

In particular embodiments, the system is configured to enable a user toselect a different template for each particular test interface. In anyembodiment described herein, the system is configured to automaticallyselect from a plurality of available templates when performing testing.In still any embodiment described herein, the system is configured toselect one or more interfaces for testing based on similar analysisperformed for one or more other websites.

In still any embodiment described herein, the system is configured touse one or more additional performance metrics when testing particularcookie consent interfaces (e.g., against one another). The one or moreadditional performance metrics may include, for example: (1) opt-inpercentage (e.g., a percentage of users that click the ‘accept all’button on a cookie consent test banner; (2) average time-to-interaction(e.g., an average time that users wait before interacting with aparticular test banner); (3) average time-to-site (e.g., an average timethat it takes a user to proceed to normal navigation across an entitysite after interacting with the cookie consent test banner; (4) dismisspercentage (e.g., a percentage of users that dismiss the cookie consentbanner using the close button, by scrolling, or by clicking ongrayed-out website); (5) functional cookies only percentage (e.g., apercentage of users that opt out of any cookies other than strictlynecessary cookies); (6) performance opt-out percentage; (7) targetingopt-out percentage; (8) social opt-out percentage; (9) etc. In stillother embodiments, the system may be configured to store other consentdata related to each of interfaces under testing such as, for example:(1) opt-in percentage by region; (2) opt-in percentage based on knowncharacteristics of the individual data subjects and/or users (e.g., age,gender, profession, etc.); and/or any other suitable data related toconsent provision. In such embodiments, the system may be configured tooptimize consent conversion by presenting a particular visitor to awebpage that is tailored to the particular visitor based at least inpart on both analyzed consent data for one or more test interfaces andon or more known characteristics of the particular visitor (e.g., agerange, gender, etc.).

In particular embodiments, the system is configured to utilize one ormore performance metrics (e.g., success criteria) for a particularinterface based at least in part on one or more regulatory enforcementcontrols. For example, the system may be configured to optimize consentprovision via one or more interfaces that result in a higher level ofcompliance with one or more particular legal frameworks (e.g., for aparticular country). For example, the system may be configured todetermine that a first interface has a more optimal consent conversionfor a first jurisdiction, even if the first interface results in a loweroverall level of consent (e.g., than a second interface) in response todetermining that the first interface results in a higher provision of aparticular type of consent (e.g., a particular type of consent requiredto comply with one or more regulations in the first jurisdiction). Inparticular embodiments, the one or more interfaces (e.g., under testing)may, for example, vary based on: (1) color; (2) text content; (3) textpositioning; (4) interface positioning; (5) selector type; (6) time atwhich the user is presented the consent interface (e.g., after being ona site for at least a particular amount of time such as 5 seconds, 10seconds, 30 seconds, etc.).

Exemplary Consent Conversion Optimization System Architecture

FIG. 60 is a block diagram of a Consent Conversion Optimization System6100 according to a particular embodiment. In some embodiments, theConsent Conversion Optimization System 6100 is configured to interfacewith at least a portion of each respective organization's PrivacyCompliance System in order generate, capture, and maintain a record ofone or more consents to process, collect, and or store personal datafrom one or more data subjects.

As may be understood from FIG. 61, the Consent Conversion OptimizationSystem 6100 includes one or more computer networks 6115, a ConsentReceipt Management Server 6110, a Consent Interface Management Server6120 (e.g., which may be configured to enable a user to setup one ormore different cookie consent user interfaces using one or moretemplates), One or More Third Party Servers 6130, one or more databases6140 (e.g., which may be used to store one or more interfaces fortesting), and one or more remote computing devices 6150 (e.g., a desktopcomputer, laptop computer, tablet computer, etc.). In particularembodiments, the one or more computer networks 6115 facilitatecommunication between the Consent Receipt Management Server 6110, aConsent Interface Management Server 120, One or More Third Party Servers6130, one or more databases 6140, and one or more remote computingdevices 6150.

The one or more computer networks 6115 may include any of a variety oftypes of wired or wireless computer networks such as the Internet, aprivate intranet, a public switch telephone network (PSTN), or any othertype of network. The communication link between Consent InterfaceManagement Server 6120 and Database 6140 may be, for example,implemented via a Local Area Network (LAN) or via the Internet.

Consent Conversion Optimization System

Various embodiments of a Consent Conversion Optimization System 6100 maybe implemented in the context of any suitable system (e.g., a privacycompliance system). For example, the Consent Conversion OptimizationSystem 6100 may be implemented to analyze and/or compare one or moretest interfaces for obtaining consent from one or more users for the useof cookies in the context of one or more particular websites. Inparticular embodiments, the system may implement one or more modules inorder to at least partially ensure compliance with one or moreregulations (e.g., legal requirements) related to the use of cookies(e.g., as discussed herein). Various aspects of the system'sfunctionality may be executed by certain system modules, including aConsent Conversion Optimization Module 6100.

Although this module is presented as a series of steps, it should beunderstood in light of this disclosure that various embodiments of theConsent Conversion Optimization Module 6100 described herein may performthe steps described below in an order other than in which they arepresented. In still other embodiments, the Consent ConversionOptimization Module 6100 may omit certain steps described below. Invarious other embodiments, the Consent Conversion Optimization Module300 may perform steps in addition to those described (e.g., such as oneor more steps described with respect to one or more other modules,etc.).

FIG. 61 depicts exemplary steps that the system may perform whenexecuting the Consent Conversion Optimization Module 6100. In particularembodiments, a Consent Conversion Optimization Module 6100 is configuredto: (1) receive and/or retrieve at least two test interfaces forenabling users to provide cookie consent (e.g., as described herein);(2) perform a/b testing using each of the at least two test interfaceson at least a respective proportion of a population of users that visitsa particular website; (3) analyze results of the a/b testing todetermine which of the at least two test interfaces leads to a higherincidence of users providing desired consent; and (4) automaticallyimplement the more successful test interface based on the analyzedresults. In other embodiments, the system is further configured to: (1)set a threshold and/or minimum sample size of testing for each of the atleast two test interfaces (e.g., automatically or based on user input);(2) generate a dashboard configured to display data associated with theanalysis; (3) etc.

As may be understood from FIG. 61, when executing the Consent ConversionOptimization Module 6100, the system begins, at Step 6110, by receiving,from a first user via a first computing device (e.g., a remote computingdevice 6150 such as any of the one or more remote computing devices 6150shown in FIG. 60), a request to access a website, and, in response tothe request, determining whether the first user has previously consentedto the use of one or more cookies by the website. In variousembodiments, as discussed above, the system may be configured to onlypresent a cookie consent interface to a user that has not: (1) alreadyvisited the website and provided consent; (2) already visited thewebsite and elected not to provide consent; (3) already visited thewebsite/webpage and provided less than a level of consent desired by thewebsite administrator; etc.

Continuing to Step 6120, the system is configured to, in response todetermining that the first user has not previously consented to the useof one or more cookies by the website, cause the first computing deviceto display a first cookie consent interface from a group of at least twotest consent interfaces. As may be understood in light of thisdisclosure, the first cookie consent interface may include a suitableinterface (e.g., Interface A stored in the One or More Databases 6140 ofFIG. 60) from a group of interfaces under testing. In variousembodiments, the system is configured to select the first interface todisplay to the user randomly from the group of interfaces under testing.In other embodiments, the system is configured to alternate betweenand/or among test interfaces to display to each new user of (e.g.,individual accessing) the website (e.g., via a particular webpage,domain, etc.). In still other embodiments, the system is configured toadhere to a particular proportion of the various interfaces undertesting (e.g., ensuring that 50% of website visitors are presented witha first interface and the other 50% are presented with a secondinterface, etc.). In some embodiments, the system is configured toperform these testing steps until at least a particular number of datapoints regarding each interface have been collected (e.g., asufficiently large sample size, a predefined number of tests, etc.). Inparticular embodiments, the system is configured to present visitors toa particular web domain with a test interface based on a user-providedweight for each particular interface under testing.

In some embodiments, the system may be configured to generate theconsent interfaces for testing. In other embodiments, the system isconfigured to receive one or more test templates created by a user(e.g., using one or more templates, or using any suitable techniquedescribed herein).

Next, at Step 6130, the system is configured to collect consent data forthe first user based on selections made by the first user via the firstcookie consent interface. When collecting consent data, the system may,for example collect data such as: (1) what particular types of cookiesthe user consented to the use of; (2) location data related to thosecookies consented to within the interface (e.g., a location of theinterface, a location of a user-selectable button or other indicia foreach particular type of cookie, etc.); (3) information associated withhow consent is collected (e.g., a check box, slider, radio button,etc.); (4) information associated with a page or screen within theinterface on which the various consented to cookie types appear (e.g.,as may be understood from FIGS. 62-70); (5) a number of users thatprovided at least some consent to particular types of cookies throughthe interface; (6) a number of types of cookies each user consented to,if at all; (7) a geographic location of each user as the system receives(e.g., or doesn't receive) consent from each user; (8) one or morecharacteristics of each use to which each particular interface ispresented (e.g., age, gender, interests, employment information, and anyother suitable known information); and (9) any other suitableinformation.

Continuing to Step 6140, the system is configured to repeat Steps6110-6130 for a plurality of other users of the website, such that eachof the at least two consent interfaces are displayed to at least aportion of the plurality of other users. In various embodiments each ofthe users of the website include any user that accesses a particularwebpage of the website. In particular embodiments, each user of thewebsite includes any user that accesses a particular web domain. As maybe understood from this disclosure, the system may, for example, repeatthe testing steps described herein until the system has collected atleast enough data to determine which of the at least two interfacesresults in a higher rate of consent provision by users (e.g., or resultsin a higher success rate based on a user-provided criteria, such as acriteria provided by a site administrator or other suitable individual).

Returning to Step 6150, the system is configured to analyze the consentdata to identify a particular interface of the at least two consentinterfaces under testing that results in a more desired level of consent(e.g., that meets the success criteria). The system may, for example,determine which interface resulted in a greater percentage of obtainedconsent. The system may also determine which interface resulted in ahigher provision of a particular type of consent. For example, thesystem may determine which interface led to provision, by end users, ofa higher rate of consent for particular types of cookies (e.g.,performance cookies, targeting cookies, etc.). The system may be furtherconfigured to analyze, based on other consent data, whether provision ofconsent may be related to particular aspects of the user interface(e.g., a location of a radio button or other input for providing theconsent, etc.). The system may further be configured to cross referencethe analyzed consent data against previously recorded consent data(e.g., for other interfaces).

In response to identifying the particular interface at Step 6150, thesystem is configured, at Step 6160, to store the particular interface inmemory for use as a site-wide consent interface for all users of thewebsite. The system may, for example, utilize the more ‘successful’interface for all future visitors of the website (e.g., because the useof such an interface may lead to an overall higher rate of consent thananother interface or combination of different interfaces).

Finally, at Step 6170, the system may be configured to optionally repeatSteps 6110-6160 using one or more additional test consent interfaces.The system may, for example, implement a particular interface forcapturing consent after performing the initial analysis described above,and then introduce a potential new test interface that is developedlater on. The system may then test this new test interface against theoriginal choice to determine whether to switch to the new interface orcontinue using the existing one.

Exemplary End-User Experience of Consent Interfaces under Testing

FIGS. 62-70 depict exemplary screen displays and interfaces that a usermay encounter when accessing a website (e.g., a particular webpage of awebsite) that requires the user to provide consent for the use ofcookies. As may be understood from these figures, particular interfacesmay utilize different arrangements and input types in order to attemptto obtain consent from end-users. FIG. 62, for example, depicts anexemplary cookie banner 6200, which may, for example, appear on anysuitable portion of webpage (e.g., on the top of the webpage, on thebottom of the webpage, in the center or center portion of the webpage,as a pop up, integrated within the webpage itself, etc.). The banner6200 may, for example, appear on a user's initial visit to a particularwebpage. As may be understood from FIG. 62, a cookie banner 6200 such asthe one depicted may enable a user (e.g., a visitor to a webpage) toaccept all cookies with the click of a single button 6205. The banner6200 may include a link 6210 to the entity that maintains the webpage'sCookie Policy.

In FIGS. 63 and 64, for example, the interface displays informationabout all types of cookies on a single screen along with an ability forthe user to provide consent for each specific cookie type through thesingle interface screen. FIGS. 63 and 64 differ, however, in the mannerin which the user provides consent. In FIG. 63, the interface 6300 usessliders, while in FIG. 64, the interface 6400 utilizes radio buttons. Asmay be understood from FIG. 63, a user is unable to opt out of strictlynecessary cookies, but may select an appropriate slider 6305, 6310 toenable/disable functional cookies and/or performance cookies. As may beunderstood from FIG. 62, a user is also unable to opt out of strictlynecessary cookies, but may select an appropriate radio button 6405, 6410to enable/disable functional cookies and/or performance cookies. In aparticular implementation, the system may be configured to test theinterfaces of FIGS. 63 and 64 against one another to determine whetherusers are more likely to provide the desired consent using one type ofselector or another.

FIGS. 65-68 depict an exemplary interface with which a user can provideconsent for the use of cookies according to another example. In theexample shown in these Figures, specific types of cookies are separatedin the interface between different pages that the user must individuallyselect, providing consent for each cookie type on the respective screen(e.g., page). As may be understood from these Figures, the interfacescontain information about the types of cookies and the purpose of theiruse, while enabling the user to provide consent for each type of cookie.The user may, for example, need to cycle within a privacy preferencecenter among the following interfaces shown in FIGS. 65-68, and 70: (1)an initial privacy interface 6500 that describes an overall privacypolicy (e.g., in FIG. 65); (2) a strictly necessary cookie interface6600 that provides information about strictly necessary cookies used bythe webpage, but does not enable the user to opt out of strictlynecessary cookies (e.g., because strictly necessary cookies may notrequire consent from users (e.g., in FIG. 66); (3) a performance cookieinterface 6700 that provides information about performance cookies usedby the webpage, and enables the user to activate a slider 6705 toenable/disable performance cookies (e.g., in FIG. 6700); (4) a targetingcookie interface 6800 that provides information about targeting cookiesused by the webpage, and enables the user to activate a slider 6805 toenable/disable targeting cookies (e.g., in FIG. 68); (5) an advertisingcookie interface 7000 that provides information about advertisingcookies used by the webpage, and enables the user to activate a slider7005 to enable/disable all advertising cookies or activate individualsliders 7010 to enable/disable particular advertising cookies (e.g., inFIG. 70); (6) etc. FIG. 69 depicts an interface 6900 such as thetargeting cookie interface 6800 of FIG. 68, with the slider 6905 set todisable targeting cookies.

The system, in various embodiments, may be configured to test aninterface in which all cookie information is shown on a single page(e.g., such as the interfaces shown in FIG. 63 or 64) against the typeof interface shown in FIGS. 65-68 to determine whether one or the otheris more likely to result in a higher rate of consent by end-users. Inparticular embodiments, the system may further analyze whetherparticular types of cookies (e.g., presented on earlier pages/screens ofthe interface or occurring earlier on the listing of cookies on theleft-hand side of the interface) are more likely to be consented to byusers.

FIG. 70 depicts a user interface 7000 where a user can provide consentfor a particular type of cookies, and then separately consent to eachparticular cookie of that type used by the website.

These various types of interfaces and others may be utilized by thesystem in testing one or more ways in which to optimize consent receiptfrom end users in the context of the system described herein.

Exemplary Consent Conversion Optimization Testing Initialization UserExperience

FIGS. 71-75 depict exemplary screen displays and graphical userinterfaces (GUIs) for enabling a user (e.g., an administrator of aparticular webpage or website) to generate and implement one or more newconsent interface tests, review existing consent interface tests, etc.

FIG. 71 depicts an exemplary interface 7100 that a user may encounterwhen accessing a listing of current, active consent conversion teststhat a particular entity, individual, or other has implemented. Forexample, the interface 7100 depicts a listing 7110 of active tests andincludes information such as, for example: (1) a name of each test; (2)a status of each test; (3) a creator of each test; (4) a start date ofeach test; and (5) information about when each test was last modified.From the listing of tests 7110, a user may select an individual test toview more data about the specific teste such as, for example: (1) anumber of interfaces being tested (e.g., tested against one another todetermine which of the interfaces results in a higher consent provisionby individuals accessing a particular domain; (2) a distributionproportion of each interface being tested as part of a particular test(e.g., a breakdown, percentage, etc.); (3) a description of the test;(4) a domain at which the test is being undertaken (e.g.,www.example.com); and/or (5) any other suitable information about eachparticular test. In particular embodiments, the interface 7100 shown inFIG. 71 further includes a selectable “New Test” Button 7150, that auser may select in order to initiate a new interface test between/amongone or more test interfaces.

FIG. 72 depicts a test creation interface 7200 according to a particularembodiment that includes one or more user-fillable fields 7205 forproviding information regarding a new test (e.g., new consent interfacetest) that a user would like to initiate. As may be understood from FIG.72, the test creation interface may include, for example, one or moreuser-fillable fields via which a user may provide: (1) a number ofinterfaces being tested (e.g., tested against one another to determinewhich of the interfaces results in a higher consent provision byindividuals accessing a particular domain; (2) a distribution proportionof each interface being tested as part of a particular test (e.g., abreakdown, percentage, etc.); (3) a description of the test; (4) adomain at which the test is being undertaken (e.g., www.example.com);and/or (5) any other suitable information about each particular test. Instill other embodiments, the test creation interface 7200 may enable auser to provide a name for the test. In some embodiments, the testcreation interface is configured to enable a user to select from one ormore template variants for use in the test. In any embodiment describedherein, the template variants may include one or more pre-created testvariants. In other embodiments, the system is configured to enable auser to create one or more test variants for use in a particular test(e.g., using any suitable technique, such as any technique describedherein). In particular embodiments, the user may then select aparticular proportion to apply to each interface being tested (e.g., asa percentage, as an equal distribution, etc.). In various embodiments,the system may be configured to present a particular interface of thetest interfaces to present to each visitor to the domain based on theuser-provided weight during test creation.

FIG. 73 depicts a test summary interface 7300 according to a particularembodiment. In the test summary interface 7300 depicted in FIG. 73, theinterface includes a summary of the interface variants under testing andthe user-selected proportion for each variant. As may be understood fromthis figure, particular test interface variants may include similarinterfaces positioned at different location within a webpage (e.g.,top/bottom, etc.). In still other embodiments, the test interfacevariants may be substantially similar looking with a different colorscheme (e.g., dark theme vs. light theme). In particular embodiments,after reviewing the test summary, the user may initiate the new test byselecting a “Start Test” Button 7305.

FIGS. 74 and 75 depict a details page 7400 of the test summary that theuser may review prior to initiating the new test. As may be understoodfrom these figures, the details page includes a dropdown 7405 via whichthe user may select a success criterion for the test. In particularembodiments, the success criteria may determine a criterion fordetermining which of the particular test interfaces results in the moredesired type and/or level of consent provided by users of the webpage.For example, the success criteria may be selected from one or moreoptions such as: (1) opt-in percentage; (2) total number of opt-ins; (3)number of visitors; and/or (4) any other suitable criterion.

Data-Processing Consent Refresh, Re-Prompt, and Recapture Systems

In particular embodiments, the consent receipt management system isconfigured to: (1) automatically cause a prior, validly received consentto expire (e.g., in response to a triggering event); and (2) in responseto causing the previously received consent to expire, automaticallytrigger a recapture of consent. In particular embodiments, the systemmay, for example, be configured to cause a prior, validly receivedconsent to expire in response to one or more triggering events such as:(1) a passage of a particular amount of time since the system receivedthe valid consent (e.g., a particular number of days, weeks, months,etc.); (2) one or more changes to a purpose of the data collection forwhich consent was received (e.g., or one or more other changes to one ormore conditions under which the consent was received; (3) one or morechanges to a privacy policy associated with the consent; (3) one or morechanges to one or more rules (e.g., laws, regulations, etc.) that governthe collection or demonstration of validly received consent; and/or (4)any other suitable triggering event or combination of events. Inparticular embodiments, such as any embodiment described herein, thesystem may be configured to link a particular consent received from adata subject to a particular version of a privacy policy, to aparticular version of a web form through which the data subject providedthe consent, etc. The system may then be configured to detect one ormore changes to the underlying privacy policy, consent receiptmethodology, etc., and, in response, automatically expire one or moreconsents provided by one or more data subjects under a previous versionof the privacy policy or consent capture form.

In various embodiments, the system may be configured to substantiallyautomatically expire a particular data subject's prior provided consentin response to a change in location of the data subject. The system may,for example, determine that a data subject is currently located in ajurisdiction, country, or other geographic location other than thelocation in which the data subject provided consent for the collectionand/or processing of their personal data. The system may be configuredto determine that the data subject is in a new location based at leastin part on, for example, a geolocation (e.g., GPS location) of a mobilecomputing device associated with the data subject, an IP address of oneor more computing devices associated with the data subject, etc.). Asmay be understood in light of this disclosure, one or more differentcountries, jurisdictions, etc. may impose different rules, regulations,etc. related to the collection, storage, and processing of personaldata. As such, in response to a user moving to a new location (e.g., orin response to a user temporarily being present in a new location), thesystem may be configured to trigger a recapture of consent based on oneor more differences between one or more rules or regulations in the newlocation and the original location from which the data subject providedconsent. In some embodiments, the system may substantially automaticallycompare the one or more rules and/or regulations of the new and originallocations to determine whether a recapture of consent is necessary.

In particular embodiments, in response to the automatic expiration ofconsent, the system may be configured to automatically trigger arecapture of consent (e.g., based on the triggering event). The systemmay, for example, prompt the data subject to re-provide consent using,for example: (1) an updated version of the relevant privacy policy; (2)an updated web form that provides one or more new purposes for thecollection of particular personal data; (3) one or more web forms orother consent capture methodologies that comply with one or more changesto one or more legal, industry, or other regulations; and/or (4) etc.

In still other embodiments, the system is configured to re-prompt anindividual (e.g., data subject) to provide consent (e.g., re-consent) toone or more transactions to which the data subject did not initiallyprovide consent. In such embodiments, the system may be configured toseek consent for one or more types of data processing in one or moresituations in which the data subject's consent has not expired (e.g., inone or more situations in which the data subject has never providedconsent). For example, when storing or retrieving information from anend user's device, an entity may be required to receive consent from theend user for such storage and retrieval. Web cookies are a commontechnology that may be directly impacted by the consent requirementsdiscussed herein. Accordingly, an entity that use cookies (e.g., on oneor more webpages) may be required to use one or more banners, pop-ups orother user interfaces on the website in order to capture consent fromend-users to store and retrieve cookie data.

In various embodiment, the use of such cookies may be necessary for awebsite to fully function. In response to a user not providing fullconsent to the use of cookies, a particular website may not functionproperly (e.g., because without the consent, the site cannot useparticular cookies).

In various embodiments, in response to identifying particular cookies(e.g., or other transactions) that a data subject has not consented to,the system may be configured to prompt the data subject to reconsent.The system may, for example, substantially automatically prompt the datasubject to reconsent in response to determining that the user (e.g.,data subject) has requested that the website perform one or morefunctions that are not possible without a particular type of consentfrom the data subject (e.g., a particular type of consent that the userinitially refused to provide. The system may, for example, prompt theuser to reconsent in time for a certain interaction with the website.

In still other embodiments, the system is configured to prompt the userto reconsent (e.g., provide consent for one or more items that the datasubject previously did not consent to) in response to one or more otherconditions such as, for example: (1) a passage of a particular amount oftime since the last time that the system prompted the user to provideconsent; (2) a change in the user's location (e.g., based on one or moresystem-determined locations of the user); (3) in response to determiningthat the user has accessed at least a particular number of additionalwebpages on a particular website (e.g., page views): (4) in response todetermining that the user's use of the particular website has changed(e.g., the user has begun attempting to use additional features, theuser visits the website more often, etc.).

In various embodiments, a Consent Refresh, Re-Prompt, and RecaptureSystem may be configured to refresh a prior, validly provided consentprior to an expiration of the consent. For example, in particularembodiments, one or more legal or industry regulations may require anentity to expire a particular consent if the entity does not undertake aparticular activity (e.g., processing activity) for which that consentwas given for a particular amount of time. For example, a visitor to awebpage may provide the visitor's e-mail address and consent to e-mailmarketing from a controlling entity of the webpage. In variousembodiments, the visitor's consent to e-mail marketing may automaticallyexpire in response to a passage of a particular amount of time withoutthe controlling entity sending any marketing e-mails. In suchembodiments, the Consent Refresh, Re-Prompt, and Recapture System may beconfigured to: (1) identify particular consents (e.g., by analyzingconsent receipt or other consent data) that the entity has received thatare set to expire due to inaction by the entity; and (2) in response toidentifying the particular consents that are set to expire due toinaction by the entity, automatically taking an action to refresh thoseparticular consents (e.g., by automatically sending a new marking e-mailprior to a time when a user's consent to such e-mail marketing wouldautomatically expire as a result of a passage of time since a marketinge-mail had been sent). In this way, the system may be configured toautomatically refresh or renew a user's consent that may otherwiseexpire as a result of inaction.

Example Consent Refresh, Re-Prompt, and Recapture System Architecture

FIG. 76 is a block diagram of a Consent Refresh, Re-Prompt, andRecapture System 7600 according to a particular embodiment. In variousembodiments, the Consent Refresh, Re-Prompt, and Recapture System 7600is configured to interface with a Consent Receipt Management System inorder to, for example: (1) monitor previously provided consent by one ormore data subjects that may be subject to future expiration; (2) monitora data subject's activity to anticipate the data subject attempting anactivity that may require a level of consent (e.g., for the processingof particular data subject data) that is higher than the system hasreceived; and/or (3) identify other changes in circumstances ortriggering events for a data subject that may warrant a refresh orrecapture (e.g., or attempted capture) of a particular required consent(e.g., required to enable an entity to properly or legally execute atransaction with a data subject). The system may then be configured toautomatically trigger a refresh of a previously provided consent, ortrigger a recapture (e.g., and/or recapture attempt) of an expired orpreviously unprovided consent.

As may be understood from FIG. 76, the Consent Refresh, Re-Prompt, andRecapture System 7600 includes one or more computer networks 7615, aConsent Receipt Management Server 7610, a Consent Refresh, Re-Prompt,and Recapture Server 7620 (e.g., which may be configured to identifyexpired consent, consents that are about to expire, etc.; and trigger anautomated action to refresh the expiring consent or recapture an expiredone, etc.), One or More Third Party Servers 7630, one or more databases7640 (e.g., which may be used to store any suitable data describedherein), and one or more remote computing devices 7650 (e.g., a desktopcomputer, laptop computer, tablet computer, etc.). In particularembodiments, the one or more computer networks 7615 facilitatecommunication between the Consent Receipt Management Server 7610, theConsent Refresh, Re-Prompt, and Recapture Server 7620, the One or MoreThird Party Servers 7630, one or more databases 7640, and one or moreremote computing devices 7650.

The one or more computer networks 7615 may include any of a variety oftypes of wired or wireless computer networks such as the Internet, aprivate intranet, a public switch telephone network (PSTN), or any othertype of network. The communication link between Consent Refresh,Re-Prompt, and Recapture Server 7620 and Database 7640 may be, forexample, implemented via a Local Area Network (LAN) or via the Internet.

The diagrammatic representation of the computer 200 shown in FIG. 2 may,for example, be used within the context of the Consent Refresh,Re-Prompt, and Recapture System 7600, for example, as a client computer(e.g., one or more remote computing devices 7650 shown in FIG. 76), oras a server computer (e.g., Consent Refresh, Re-Prompt, and RecaptureServer 7620 shown in FIG. 76). In particular embodiments, the computer200 may be suitable for use as a computer within the context of theConsent Refresh, Re-Prompt, and Recapture System 7600 that is configuredto: (1) analyze one or more consent receipts to identify one or morevalid consents for the processing of personal data that will expire at afuture time in response to the occurrence of at least one particularcondition; and (2) in response to identifying the one or more validconsents for the processing of personal data that will expire at afuture time in response to the occurrence of at least one particularcondition, automatically initiating an action to refresh the one or morevalid consents; and/or (1) receive an indication that a user has atleast initially withheld consent; (2) identify an occurrence of one ormore conditions; and (3) in response to identifying the occurrence ofthe one or more conditions, re-prompting the user to provide theconsent.

Data Processing Consent Refresh, Re-Prompt, and Recapture Systems andRelated Methods

Various embodiments of a Consent Refresh, Re-Prompt, and RecaptureSystem 7600 may be implemented in the context of any suitable system(e.g., a privacy compliance system). For example, the Consent Refresh,Re-Prompt, and Recapture System 7600 may be implemented to maintain orsecure one or more valid consents for the processing of personal data ofone or more data subjects under a particular transaction (e.g., whichmay, for example, involve the processing, storage, etc. of personaldata). Various aspects of the system's functionality may be executed bycertain system modules, including a Consent Refresh Module 7700 and/or aConsent Re-prompting Module 7800.

Although these modules are presented as a series of steps, it should beunderstood in light of this disclosure that various embodiments of theConsent Refresh Module 7700 and the Consent Re-prompting Module 7800described herein may perform the steps described below in an order otherthan in which they are presented. In still other embodiments, theConsent Refresh Module 7700 and the Consent Re-prompting Module 7800 mayomit certain steps described below. In various embodiments, the ConsentRefresh Module 7700 and the Consent Re-prompting Module 7800 may performsteps in addition to those described (e.g., such as one or more stepsdescribed with respect to one or more other modules, etc.).

FIG. 77 depicts exemplary steps that the system may perform whenexecuting the Consent Refresh Module 7700. In particular embodiments, aConsent Refresh, Re-Prompt, and Recapture System 7600, when executingone or more steps of a Consent Refresh Module 7700 according toparticular embodiments, is configured to refresh a prior, validlyprovided consent prior to an expiration of the consent. For example, inparticular embodiments, one or more legal or industry regulations mayrequire an entity to expire a particular consent if the entity does notundertake a particular activity (e.g., processing activity) for whichthat consent was given for a particular amount of time. For example, avisitor to a webpage may provide the visitor's e-mail address andconsent to e-mail marketing from a controlling entity of the webpage. Invarious embodiments, the visitor's consent to e-mail marketing mayautomatically expire in response to a passage of a particular amount oftime without the controlling entity sending any marketing e-mails. Insuch embodiments, the Consent Refresh, Re-Prompt, and Recapture Systemmay be configured to: (1) identify particular consents (e.g., byanalyzing consent receipt or other consent data) that the entity hasreceived that are set to expire due to inaction by the entity; and (2)in response to identifying the particular consents that are set toexpire due to inaction by the entity, automatically taking an action torefresh those particular consents (e.g., by automatically sending a newmarking e-mail prior to a time when a user's consent to such e-mailmarketing would automatically expire as a result of a passage of timesince a marketing e-mail had been sent). In this way, the system may beconfigured to automatically refresh or renew a user's consent that mayotherwise expire as a result of inaction.

As may be understood from FIG. 77, when executing the Consent RefreshModule 7700, the system begins, at Step 7710, by analyzing one or moreconsent receipts (e.g., and or consent records) to identify one or morevalid consents for the processing of personal data that will expire at afuture time. In various embodiments, the system is configured toidentify one or more valid consents that will expire in response to anoccurrence of at least one particular condition.

In various embodiments, a Consent Refresh, Re-Prompt, and RecaptureSystem may be configured to refresh a prior, validly provided consentprior to an expiration of the consent. For example, in particularembodiments, one or more legal or industry regulations may require anentity to expire a particular consent if the entity does not undertake aparticular activity (e.g., processing activity) for which that consentwas given for a particular amount of time. For example, a visitor to awebpage may provide the visitor's e-mail address and consent to e-mailmarketing from a controlling entity of the webpage. In variousembodiments, the visitor's consent to e-mail marketing may automaticallyexpire in response to a passage of a particular amount of time withoutthe controlling entity sending any marketing e-mails. In suchembodiments, the Consent Refresh, Re-Prompt, and Recapture System may beconfigured to: (1) identify particular consents (e.g., by analyzingconsent receipt or other consent data) that the entity has received thatare set to expire due to inaction by the entity; and (2) in response toidentifying the particular consents that are set to expire due toinaction by the entity, automatically taking an action to refresh thoseparticular consents (e.g., by automatically sending a new marking e-mailprior to a time when a user's consent to such e-mail marketing wouldautomatically expire as a result of a passage of time since a marketinge-mail had been sent). In this way, the system may be configured toautomatically refresh or renew a user's consent that may otherwiseexpire as a result of inaction.

Continuing to Step 7720, the system, in various embodiments, isconfigured to, in response to identifying the one or more valid consentsfor the processing of personal data that will expire at a future time(e.g., in response to an occurrence of at least one particularcondition), automatically initiate an action to refresh the one or morevalid consents. This may involve, for example, automatically processinga particular type of data associated with the data subject,automatically taking one or more actions under a transaction to whichthe data subject has consented, etc.

FIG. 78 depicts exemplary steps that the system may perform whenexecuting the Consent Re-Prompting Module 7800. In particularembodiments, a Consent Refresh, Re-Prompt, and Recapture System 7600,when executing one or more steps of a Consent Refresh Module 7700according to particular embodiments, is configured re-prompt anindividual (e.g., data subject) to provide consent (e.g., re-consent) toone or more transactions to which the data subject did not initiallyprovide consent (e.g., and/or did not initially provide sufficientconsent for a particular transaction, to ensure a particular level offunctionality of a webpage or software application, etc.).

As may be understood from FIG. 78, when executing the ConsentRe-Prompting Module 7800, the system begins, at Step 7810, by promptinga user to provide initial consent for a first particular type of dataprocessing. As may be understood in light of this disclosure, a datasubject may access an interaction interface (e.g., via the web) forinteracting with a particular entity (e.g., one or more entity systems).The interaction interface (e.g., user interface) may include, forexample, a suitable website, web form, user interface etc. Theinteraction interface may be provided by the entity. Using theinteraction interface, a data subject may initiate a transaction withthe entity that requires the data subject to provide valid consent(e.g., because the transaction includes the processing of personal databy the entity). The transaction may include, for example: (1) accessingthe entity's website; (2) signing up for a user account with the entity;(3) signing up for a mailing list with the entity; (4) a free trial signup; (5) product registration; and/or (6) any other suitable transactionthat may result in collection and/or processing personal data, by theentity, about the data subject.

As may be understood from this disclosure, any particular transactionmay record and/or require one or more valid consents from the datasubject. For example, the system may prompt a particular data subject toprovide consent for each particular type of personal data that will becollected as part of the transaction. The system may, in variousembodiments, be configured to prompt the data subject to provide validconsent, for example, by: (1) displaying, via the interaction interface,one or more pieces of information regarding the consent (e.g., whatpersonal data will be collected, how it will be used, etc.); and (2)prompt the data subject to provide the consent.

Continuing to Step 7820, the system is configured to receive anindication that the user has at least initially withheld the initialconsent.

Next, at Step 7830, the system is configured to identify an occurrenceof one or more conditions. In various embodiments, the system isconfigured, at Step 7840, to re-prompt the user to provide the initialconsent (e.g., or any other suitable level of consent) in response toidentifying the occurrence of the one or more conditions.

In still other embodiments, the system is configured to re-prompt anindividual (e.g., data subject) to provide consent (e.g., re-consent) toone or more transactions to which the data subject did not initiallyprovide consent. In such embodiments, the system may be configured toseek consent for one or more types of data processing in one or moresituations in which the data subject's consent has not expired (e.g., inone or more situations in which the data subject has never providedconsent). For example, when storing or retrieving information from anend user's device, an entity may be required to receive consent from theend user for such storage and retrieval. Web cookies are a commontechnology that may be directly impacted by the consent requirementsdiscussed herein. Accordingly, an entity that use cookies (e.g., on oneor more webpages) may be required to use one or more banners, pop-ups orother user interfaces on the website in order to capture consent fromend-users to store and retrieve cookie data.

In various embodiment, the use of such cookies may be necessary for awebsite to fully function. In response to a user not providing fullconsent to the use of cookies, a particular website may not functionproperly (e.g., because without the consent, the site cannot useparticular cookies).

In various embodiments, in response to identifying particular cookies(e.g., or other transactions) that a data subject has not consented to,the system may be configured to prompt the data subject to reconsent.The system may, for example, substantially automatically prompt the datasubject to reconsent in response to determining that the user (e.g.,data subject) has requested that the website perform one or morefunctions that are not possible without a particular type of consentfrom the data subject (e.g., a particular type of consent that the userinitially refused to provide. The system may, for example, prompt theuser to reconsent in time for a certain interaction with the website.

In still other embodiments, the system is configured to prompt the userto reconsent (e.g., provide consent for one or more items that the datasubject previously did not consent to) in response to one or more otherconditions such as, for example: (1) a passage of a particular amount oftime since the last time that the system prompted the user to provideconsent; (2) a change in the user's location (e.g., based on one or moresystem-determined locations of the user); (3) in response to determiningthat the user has accessed at least a particular number of additionalwebpages on a particular website (e.g., page views): (4) in response todetermining that the user's use of the particular website has changed(e.g., the user has begun attempting to use additional features, theuser visits the website more often, etc.).

In various embodiments, the system is configured to re-prompt the uservia a suitable user interface. In various embodiments, the system isconfigured to use one or more optimized consent interfaces generatedand/or determined using any suitable technique described herein.

Data-Processing User Interface Monitoring System Overview

In various embodiments, a consent receipt management system isconfigured to generate a consent receipt for a data subject that linksto (e.g., in computer memory) metadata identifying a particular purposeof the collection and/or processing of personal data that the datasubject consented to, a capture point of the consent (e.g., a copy ofthe web form or other mechanism through which the data subject providedconsent, and other data associated with one or more ways in which thedata subject granted consent). In particular embodiments, the system maybe configured to analyze data related to consent data received from oneor more particular capture points. The one or more capture points mayinclude, for example, a webform, an e-mail inbox, website, mobileapplication, or any other suitable capture point.

In particular embodiments, the system is configured to automaticallycollect a change in capture rate for a particular capture point. Invarious embodiments, the system is configured to store time andfrequency data for consents received via a particular capture pint(e.g., consent collection point). The system may, for example, monitor arate of consent received via a particular webform on a company website.

In various embodiments, the system is configured to analyze data for aparticular capture point to identify a change in consent capture ratefrom the capture point. The system may, for example, be configured toautomatically detect that the system has stopped receiving consentrecords from a particular capture point. In such embodiments, the systemmay be configured to generate an alert, and transmit the alert to anysuitable individual (e.g., privacy team member, IT department member,etc.) regarding the capture point. The system may, for example, enablean entity to identify one or more capture points that may have becomenon-functional (e.g., as a result of one or more changes to the capturepoint). For example, in response to determining that a capture pointthat typically generates few thousand consent records per day suddenlystops generating any, the system may be configured to: (1) determinethat there is an issue with the capture point; and (2) generate and/ortransmit an alert identifying the problematic capture point. The alertmay include an alert that the system may be capturing data that does nothave an associated consent. In various embodiments, the system may beconfigured to perform an updated risk analysis for one or moreprocessing activities that are associated with the capture point inresponse to determining that the capture point is not properly capturingrequired consent.

Example User Interface Monitoring System Architecture

FIG. 80 is a block diagram of a User Interface Monitoring System 8000according to a particular embodiment. In various embodiments, the UserInterface Monitoring System 8000 is configured to interface with aConsent Receipt Management System in order to, for example: (1) monitorpreviously provided consent by one or more data subjects that may besubject to future expiration; (2) monitor a data subject's activity toanticipate the data subject attempting an activity that may require alevel of consent (e.g., for the processing of particular data subjectdata) that is higher than the system has received; and/or (3) identifyother changes in circumstances or triggering events for a data subjectthat may warrant a refresh or recapture (e.g., or attempted capture) ofa particular required consent (e.g., required to enable an entity toproperly or legally execute a transaction with a data subject). Thesystem may then be configured to automatically trigger a refresh of apreviously provided consent, or trigger a recapture (e.g., and/orrecapture attempt) of an expired or previously unprovided consent.

As may be understood from FIG. 80, the User Interface Monitoring System8000 includes one or more computer networks 8015, a Consent ReceiptManagement Server 8010, a User Interface Monitoring Server 8020 (e.g.,which may be configured to analyze data related to consent data receivedfrom one or more particular capture points), One or More Third PartyServers 8030, one or more databases 8040 (e.g., which may be used tostore any suitable data described herein), and one or more remotecomputing devices 8050 (e.g., a desktop computer, laptop computer,tablet computer, etc.). In particular embodiments, the one or morecomputer networks 8015 facilitate communication between the ConsentReceipt Management Server 8010, the User Interface Monitoring Server8020, the One or More Third Party Servers 8030, one or more databases8040, and one or more remote computing devices 8050.

The one or more computer networks 8015 may include any of a variety oftypes of wired or wireless computer networks such as the Internet, aprivate intranet, a public switch telephone network (PSTN), or any othertype of network. The communication link between User InterfaceMonitoring Server 8020 and Database 8040 may be, for example,implemented via a Local Area Network (LAN) or via the Internet.

The diagrammatic representation of the computer 200 shown in FIG. 2 may,for example, be used within the context of the User Interface MonitoringSystem 8000, for example, as a client computer (e.g., one or more remotecomputing devices 8050 shown in FIG. 80), or as a server computer (e.g.,User Interface Monitoring Server 8020 shown in FIG. 80). In particularembodiments, the computer 200 may be suitable for use as a computerwithin the context of the User Interface Monitoring System 8000 that isconfigured to: (1) automatically collect a change in capture rate for aparticular capture point; (2) store time and frequency data for consentsreceived via a particular capture pint (e.g., consent collection point);(3) monitor a rate of consent received via a particular webform on acompany website; (4) analyze data for a particular capture point toidentify a change in consent capture rate from the capture point; and/or(5) take any suitable action related to the data collected and/oranalyzed.

Data Processing User Interface Monitoring Systems and Related Methods

Various embodiments of a User Interface Monitoring System 8000 may beimplemented in the context of any suitable system (e.g., a privacycompliance system). For example, the User Interface Monitoring Systemmay be implemented to: (1) automatically collect a change in capturerate for a particular capture point; (2) store time and frequency datafor consents received via a particular capture pint (e.g., consentcollection point); (3) monitor a rate of consent received via aparticular webform on a company website; (4) analyze data for aparticular capture point to identify a change in consent capture ratefrom the capture point; and/or (5) take any suitable action related tothe data collected and/or analyzed. Various aspects of the system'sfunctionality may be executed by certain system modules, including aUser Interface Monitoring Module 8100.

Although these modules are presented as a series of steps, it should beunderstood in light of this disclosure that various embodiments of theUser Interface Monitoring Module 8100 described herein may perform thesteps described below in an order other than in which they arepresented. In still other embodiments, the User Interface MonitoringModule 8100 may omit certain steps described below. In variousembodiments, the User Interface Monitoring Module 8100 may perform stepsin addition to those described (e.g., such as one or more stepsdescribed with respect to one or more other modules, etc.).

FIG. 81 depicts exemplary steps that the system may perform whenexecuting the User Interface Monitoring Module 8100. In particularembodiments, a User Interface Monitoring System 8000 (e.g., consentcapture point monitoring system), when executing one or more steps of aUser Interface Monitoring Module 8100 according to particularembodiments, is configured to: (1) automatically collect a change incapture rate for a particular capture point; (2) store time andfrequency data for consents received via a particular capture pint(e.g., consent collection point); (3) monitor a rate of consent receivedvia a particular webform on a company website; (4) analyze data for aparticular capture point to identify a change in consent capture ratefrom the capture point; and/or (5) take any suitable action related tothe data collected and/or analyzed.

As may be understood from FIG. 81, when executing the User InterfaceMonitoring Module 8100, the system begins, at Step 8110, by providing auser interface at a particular capture point for initiating atransaction between an entity and a data subject. In variousembodiments, the transaction involves the collection and/or processingassociated with the data subject by the entity (e.g., by one or moreentity systems).

As may be understood from this disclosure, a data subject may access aninteraction interface (e.g., via the web) for interacting with aparticular entity (e.g., one or more entity systems). The interactioninterface (e.g., user interface) may include, for example, a suitablewebsite, webpage, web form, user interface, etc. (e.g., located at anysuitable domain). The interaction interface may be provided by theentity. Using the interaction interface, a data subject may initiate atransaction with the entity that requires the data subject to providevalid consent (e.g., because the transaction includes the processing ofpersonal data by the entity). The transaction may include, for example:(1) accessing the entity's website; (2) signing up for a user accountwith the entity; (3) signing up for a mailing list with the entity; (4)a free trial sign up; (5) product registration; and/or (6) any othersuitable transaction that may result in collection and/or processingpersonal data, by the entity, about the data subject.

As may be understood from this disclosure, any particular transactionmay record and/or require one or more valid consents from the datasubject. For example, the system may require a particular data subjectto provide consent for each particular type of personal data that willbe collected as part of the transaction. The system may, in variousembodiments, be configured to prompt the data subject to provide validconsent, for example, by: (1) displaying, via the interaction interface,one or more pieces of information regarding the consent (e.g., whatpersonal data will be collected, how it will be used, etc.); and (2)prompt the data subject to provide the consent.

Continuing to Step 8120, the system is configured to receive, from arespective computing device associated with each of a plurality of datasubjects via the user interface, a plurality of requests to initiate thetransaction between the entity and each respective data subject for theplurality of data subjects.

Next, at Step 8130, the system is configured for, in response toreceiving each of the plurality of requests: (1) generating a uniqueconsent receipt key for each respective request; and (2) storing arespective consent record for each respective request, the respectiveconsent record comprising the unique consent receipt key. In response toa particular data subject (e.g., or the entity) initiating thetransaction, the system may, for example, be configured to: (1) generatea unique receipt key (e.g., unique receipt ID); (2) associate the uniquereceipt key with the data subject (e.g., a unique subject identifier),the entity, and the transaction; and (3) electronically store (e.g., incomputer memory) the unique receipt key. The system may further store aunique user ID (e.g., unique subject identifier) associated with thedata subject (e.g., a hashed user ID, a unique user ID provided by thedata subject, unique ID based on a piece of personal data such as ane-mail address, etc.).

At Step 8140, the system is configured to monitor the particular capturepoint to determine a rate of consent records generated in response torequests received via the user interface (e.g., at a particular capturepoint). The system may, for example, be configured to track data relatedto a particular capture point (e.g., one or more particular userinterfaces at a particular capture point) to determine a transactioninitiation rate for the capture point (e.g., a rate at which one or moredata subjects provide consent via the particular capture point).

Continuing to Step 8150, the system is configured to identify a changein the rate of consent records generated at the particular capturepoint. The system may, for example, be configured to identify a decreasein the rate of consent records generated at a particular capture point.For example, the system may be configured to automatically detect thatthe system has stopped receiving consent records from a particularcapture point. In various embodiments, the capture point may comprise,for example: (1) a webpage; (2) a domain; (3) a web application; (4) asoftware application; (5) a mobile application; and/or (6) any othersuitable consent capture point.

Next, at Step 8160, the system is configured to, in response toidentifying the change in the rate of consent records generated at theparticular capture point, generate an electronic alert and transmit thealert to an individual responsible for the particular capture point. Thesystem may be configured to generate an alert and transmit the alert toany suitable individual (e.g., privacy team member, IT departmentmember, etc.) regarding the capture point. The system may, for example,enable an entity to identify one or more capture points that may havebecome non-functional (e.g., as a result of one or more changes to thecapture point). For example, in response to determining that a capturepoint that typically generates few thousand consent records per daysuddenly stops generating any, the system may be configured to: (1)determine that there is an issue with the capture point; and (2)generate and/or transmit an alert identifying the problematic capturepoint. The alert may include an alert that the system may be capturingdata that does not have an associated consent. In various embodiments,the system may be configured to perform an updated risk analysis for oneor more processing activities that are associated with the capture pointin response to determining that the capture point is not properlycapturing required consent.

Exemplary Consent Capture Point Monitoring User Experience

FIGS. 82-85 depict exemplary screen displays and graphical userinterfaces (GUIs) for enabling a user (e.g., an administrator of aparticular webpage or website) to access consent capture point data andother data.

FIG. 82 depicts an exemplary collection point data interface 8200according to a particular embodiment. As may be understood from FIG. 82,the collection point data interface 8200 may include, for example: (1) adata of activation of a particular collection point (e.g., capturepoint); (2) a name of the collection point; (3) a description of thecollection point; (4) a purpose of the collection point; (5) a URL atwhich the collection point is located/hosted/accessible; (6) a PrivacyPolicy URL related to the collection point; (7) a data subjectidentifier utilized by the collection point (e.g., e-mail); (8) aconsent interaction type (e.g., form submission, implied consent throughscrolling, time-on-site, etc.); (9) data related to double opt-inrequirements at the collection point, etc.

FIG. 83 depicts a transaction record 8300 according to a particularembodiment. As may be understood form FIG. 83, the transaction record8300 displays a listing of recent transactions and additional datarelated to, for example: (1) a collection point at which the transactionwas initiated; (2) a time at which the transaction was initiated; (3) atransaction number; (4) a receipt ID; and other suitable dat.

FIGS. 84 and 85 depict exemplary collection point consent collectiondata. As may be understood from FIG. 84, the user interface 8400depicted displays transaction and consent receipt data for a particularcapture point (e.g., collection point). The data includes, for example,consent rate data for the collection point (e.g., which may be utilizedin the context of any consent interface testing systems describedherein). FIG. 85 depicts a user interface 8500 hat displays comparativedata for two or more different collection points. As may be understoodfrom this interface 8500, the system is configured to track, forexample; (1) a number of transactions originating from each collectionpoint; (2) a number of receipts (e.g., consent receipts) generated fromeach collection point; and/ (3) a consent rate for each collectionpoint.

Automated Process Blocking Systems and Methods

Various embodiments of an Automated Process blocking System may beimplemented in the context of any suitable system (e.g., a privacycompliance system). For example, the Automated Process blocking Systemmay be implemented to automatically determine whether a data subject hasprovided valid consent to a particular incidence of data processing(e.g., related to the data subject) prior to initiating and/orcompleting the data processing. Various aspects of the system'sfunctionality may be executed by certain system modules, including aConsent Confirmation and Process Blocking Module 8600.

Although this module is presented as a series of steps, it should beunderstood in light of this disclosure that various embodiments of theConsent Confirmation and Process Blocking Module 8600 described hereinmay perform the steps described below in an order other than in whichthey are presented. In still other embodiments, the Consent Confirmationand Process Blocking Module 8600 may omit certain steps described below.In various other embodiments, the Consent Confirmation and ProcessBlocking Module 8600 may perform steps in addition to those described(e.g., such as one or more steps described with respect to one or moreother modules, etc.).

FIG. 86 depicts exemplary steps that the system may perform whenexecuting the Consent Confirmation and Process Blocking Module 8600. Inparticular embodiments, a Consent Confirmation and Process BlockingModule 8600 is configured to: (1) receive an indication that one or moreentity systems are processing one or more pieces of personal dataassociated with a particular data subject; (2) in response to receivingthe indication, identifying at least one process for which the one ormore pieces of personal data are being processed; (3) determine, using aconsent receipt management system, whether the data subject has providedvalid consent for the processing of the one or more pieces of personaldata for the at least one process; (4) at least partially in response todetermining that the data subject has not provided valid consent for theprocessing of the one or more pieces of personal data for the at leastone process, automatically blocking the processing

As may be understood from FIG. 86, when executing the ConsentConfirmation and Process Blocking Module 8600, the system begins, atStep 8610, by receiving an indication that one or more computer systemshave received, collected or processed one or more pieces of personaldata associated with a data subject. In particular embodiments, the oneor more computer systems include any suitable computer system associatedwith a particular entity.

In various embodiments, the system is configured to receive anindication that one or more computer systems have received, collected orprocessed one or more pieces of personal data associated with a datasubject. In particular embodiments, the one or more computer systemsinclude any suitable computer system associated with a particularentity. In other embodiments, the one or more computer systems compriseone or more software applications, data stores, databases, etc. thatcollect, process, and/or store data (e.g., personally identifiable data)on behalf of the entity (e.g., organization). In particular embodiments,the system is configured to receive the indication through integrationwith the one or more computer systems. In a particular example, thesystem may provide a software application for installation on a systemdevice that is configured to transmit the indication in response to thesystem receiving, collecting, and/or processing one or more pieces ofpersonal data.

Continuing to Step 8620, the system is configured to determine a purposeof the receipt, collection, and/or processing of the one or more piecesof personal data.

Next, at Step 8630, the system is configured to determine, based atleast in part on the purpose and the one or more consent records,whether the data subject has provided valid consent to the receipt,collection, and/or processing of the one or more pieces of personal data(e.g., for the determined purpose). For example, particular consentrecords may record: (1) what information was provided to the consenter(e.g., data subject) at the time of consent (e.g., a privacy policy,what personal data would be collected following the provision of theconsent, for what purpose that personal data would be collected, etc.);(2) how consent was received; (3) etc. The system may then be configuredto determine whether: (1) the data subject has consented to the receipt,collection, and/or processing of the specific data being received,collected, and/or processed as well as whether the data subject hasconsented to the purpose for which the specific data is being received,collected, and/or processed. A data subject may, for example, haveconsented to the receipt, collection, and/or processing of a particulartype of personal data in the context of a different purposes. In thisexample, consent to receive, collect, and/or process particular data fora different purpose may not constitute valid consent.

For example, FIG. 42 depicts an exemplary log of consent receipts 4200for a particular transaction (e.g., the free trial signup describedabove). As shown in this figure, the system is configured to maintain adatabase of consent receipts that includes, for example, a timestamp ofeach receipt, a unique key associated with each receipt, a customer IDassociated with each receipt (e.g., the customer's e-mail address), etc.In particular embodiments, the centralized data repository systemdescribed above may be configured to cross-reference the database ofconsent receipts (e.g., or maintain the database) in response toreceiving the indication that a first party system has received, stored,and/or processed personal data (e.g., via the free trial signupinterface) in order to confirm that the data subject has provided validconsent prior to storing the indication of the personal data.

At Step 8650, the system is configured to, in response to determiningthat the data subject has provided the valid consent, proceed withreceiving, collecting, and/or processing the one or more pieces ofpersonal data (e.g., and/or maintain any such data that has already beenreceived, collected, and/or processed for which the data subject hasprovided valid consent.

In various embodiments, the system may be configured to: (1) receive theindication that the first party system has collected, stored, and/orprocessed a piece of personal data; (2) identify, based at least in parton the piece of personal data, a data subject associated with the pieceof personal data; (3) determine, based at least in part on one or moreconsent receipts received from the data subject (e.g., one or more validreceipt keys associated with the data subject), and one or more piecesof information associated with the piece of personal data, whether thedata subject has provided valid consent to collect, store, and/orprocess the piece of personal data; (4) in response to determining thatthe data subject has provided valid consent, storing the piece ofpersonal data in any manner described herein; and (5) in response todetermining that the data subject has not provided valid consent,deleting the piece of personal data (e.g., not store the piece ofpersonal data).

At Step 8650, in response to determining that the data subject has notprovided the valid consent, the system is configured to (at leasttemporarily) cease receiving, collecting, and/or processing the one ormore pieces of personal data.

In particular embodiments, in response to determining that the datasubject has not provided valid consent, the system may be furtherconfigured to: (1) automatically determine where the data subject'spersonal data is stored (e.g., by the first party system); and (2) inresponse to determining the location of the data (which may be onmultiple computing systems), automatically facilitate the deletion ofthe data subject's personal data from the various systems (e.g., byautomatically assigning a plurality of tasks to delete data acrossmultiple business systems to effectively delete the data subject'spersonal data from the systems). In particular embodiments, the step offacilitating the deletion may comprise, for example: (1) overwriting thedata in memory; (2) marking the data for overwrite; (2) marking the dataas free (e.g., and deleting a directory entry associated with the data);and/or (3) any other suitable technique for deleting the personal data.

Data Processing Systems for Verifying an Age of a Data Subject

In particular embodiments, a data processing consent management systemmay be configured to utilize one or more age verification techniques toat least partially authenticate the data subject's ability to providevalid consent (e.g., under one or more prevailing legal requirements).For example, according to one or more particular legal or industryrequirements, an individual (e.g., data subject) may need to be at leasta particular age (e.g., an age of majority, an adult, over 18, over 21,or any other suitable age) in order to provide valid consent.

In various embodiments, a consent receipt management system may beimplemented in the context of any suitable privacy management systemthat is configured to ensure compliance with one or more legal orindustry standards related to the collection and/or storage of privateinformation (e.g., such as personal data). In particular embodiments,the system is configured to manage one or more consent receipts betweena data subject and an entity. In various embodiments, a consent receiptmay include a record (e.g., a data record stored in memory andassociated with the data subject) of consent, for example, as atransactional agreement where the data subject is already identified oridentifiable as part of the data processing that results from theprovided consent.

As may be understood from this disclosure, any particular transactionmay record and/or require one or more valid consents from the datasubject. For example, the system may require a particular data subjectto provide consent for each particular type of personal data that willbe collected as part of the transaction. The system may, in variousembodiments, be configured to prompt the data subject to provide validconsent, as described herein.

The system may, for example, be configured to track data on behalf of anentity that collects and/or processes personal data related to: (1) whoconsented to the processing or collection of personal data (e.g., thedata subject themselves or a person legally entitled to consent on theirbehalf such as a parent, guardian, etc.); (2) when the consent was given(e.g., a date and time); (3) what information was provided to theconsenter at the time of consent (e.g., a privacy policy, what personaldata would be collected following the provision of the consent, for whatpurpose that personal data would be collected, etc.); (4) how consentwas received (e.g., one or more copies of a data capture form, webform,etc. via which consent was provided by the consenter); (5) when consentwas withdrawn (e.g., a date and time of consent withdrawal if theconsenter withdraws consent); and/or (6) any other suitable data relatedto receipt or withdrawal of consent.

In some embodiments, the system may be configured to verify the age ofthe data subject. The system may, for example, be configured to validatea consent provided by a data subject by authenticating an age of thedata subject. For example, the system may be configured to confirm,using any suitable technique described herein, that the data subject hasreached the age of majority in the jurisdiction in which the datasubject resides (e.g., is not a minor).

A type of transaction that the data subject is consenting to may requirethe data subject to be of at least a certain age for the data subject'sconsent to be considered valid by the system. Similarly, the system maydetermine whether the data subject's consent is valid based on the datasubject's age in response to determining one or more age restrictions onconsent in a location (e.g., jurisdiction) in which the data subjectresides, is providing the consent, etc.

For example, a data subject that is under the age of eighteen in aparticular country may not be legally able to provide consent for creditcard data to be collected as part of a transaction. The system may beconfigured to determine an age for valid consent for each particulartype of personal data that will be collected as part of any particulartransaction based on one or more factors. These factors may include, forexample, the transaction and type of personal data collected as part ofthe transaction, the country where the transaction is to occur and thecountry of the data subject, and the age of the data subject, amongothers.

In various implementations, the system may be configured to verify theage of a data subject by providing a prompt for the data subject toprovide a response to one or more questions. The response to each of theone or more questions may prompt the data subject to provide a selection(e.g., from a list) or input of data (e.g., input within a text box). Insome implementations, the system may generate a logic problem or quiz asthe prompt. The logic problem or quiz may be tailored to identify an ageof the data subject or whether the data subject is younger or older thana threshold age (e.g., the age for valid consent for the particular typeof personal data that will be collected as part of the transaction). Thelogic problem or quiz may be randomized or specific to a data subject,and in some embodiments, the logic problem or quiz may includemathematics or reading comprehension problems.

In some embodiments, the system may verify the age of a data subject inresponse to prompting the data subject to provide identifyinginformation of the data subject (e.g., via a response to one or morequestions), and then accessing a public third-party database todetermine an age of the data subject. The identifying information mayinclude, for example, a name, address, phone number, etc. of the datasubject. In some implementations, the system may erase the providedidentifying information from storage within the system after the age ofthe data subject is verified.

The system may, for example, be configured to: (1) receive, from a datasubject, a request to enter into a particular transaction with anentity, the transaction involving the collection of personal dataassociated with the data subject by the entity; (2) in response toreceiving the request, determining whether the collection of personaldata by the entity under the transaction requires the data subject to beat least a particular age; (3) at least partially in response todetermining that the transaction requires the data subject to be atleast the particular age, using one or more age verification techniquesto confirm the age of the data subject; (4) in response to determining,using the one or more age verification techniques, that the data subjectis at least the particular age, storing a consent receipt that includesdata associate with the entity, the data subject, the age verification,and the transaction; and (5) initiating the transaction between the datasubject and the entity.

In particular embodiments, a particular entity may systematicallyconfirm an age (e.g., or prompt for parental consent as described below)as a matter of course. For example, particular entities may provide oneor more products or services that are often utilized and/or consumed byminors (e.g., toy companies). Such entities may, for example, utilize asystem described herein such that the system is configured toautomatically verify the age of every data subject that attempts toenter into a transaction with the entity. For example, Lego may requireany user registering for the Lego website to verify that they are over18, or, alternatively, to use one of the guardian/parental consenttechniques described below to ensure that the entity has the consent ofa guardian of the data subject in order to process the data subject'sdata.

In various embodiments, the one or more age verification techniques mayinclude, for example: (1) comparing one or more pieces of informationprovided by the data subject to one or more pieces of publicly availableinformation (e.g., in one or more databases, credit bureau directories,etc.); (2) prompting the data subject to provide one or more response toone or more age-challenge questions (e.g., brain puzzles, logicproblems, math problems, vocabulary questions, etc.); (3) prompting thedata subject to provide a copy of one or more government issuedidentification cards, receiving an input or image of the one or moregovernment identification cards, confirming the authenticity of the oneor more government identification cards, and confirming the age of thedata subject based on information from the one or more governmentidentification cards; (4) etc. In response to determining that the datasubject is not at least the particular required age, the system may beconfigured to prompt a guardian or parent of the data subject to provideconsent on the data subject's behalf (e.g., as described below).

Data Processing Systems for Prompting a Guardian to Provide Consent onBehalf of a Minor Data Subject

In various embodiments, the system may require guardian consent (e.g.,parental consent) for a data subject. The system may prompt the datasubject to initiate a request for guardian consent or the system mayinitiate a request for guardian consent without initiation from the datasubject (e.g., in the background of a transaction). In some embodiments,the system may require guardian consent when a data subject is under theage for valid consent for the particular type of personal data that willbe collected as part of the particular transaction. The system may usethe any age verification method described herein to determine the age ofthe data subject. Additionally, in some implementations, the system mayprompt the data subject to identify whether the data subject is younger,at least, or older than a particular age (e.g., an age for valid consentfor the particular type of personal data that will be collected as partof the particular transaction), and the system may require guardianconsent when the data subject identifies an age younger than theparticular age.

In various embodiments, the system may be configured to communicate viaelectronic communication with the identified guardian (e.g., parent) ofthe data subject. The electronic communication may include, for example,email, phone call, text message, message via social media or athird-party system, etc. In some embodiments, the system may prompt thedata subject to provide contact information for the data subject'sguardian. The system may provide the electronic communication to thecontact information provided by the data subject, and prompt theguardian to confirm they are the guardian of the data subject. In someembodiments, the system may provide a unique code (e.g., a six-digitcode, or other unique code) as part of the electronic communicationprovided to the guardian. The guardian may then provide the receivedunique code to the data subject, and the system may enable the datasubject to input the unique code to the system to confirm guardianconsent. In some embodiments, the system may use blockchain between anelectronic device of the guardian and the system and/or an electronicdevice of the data subject to confirm guardian consent.

In various implementations, the system may include an electronicregistry of guardians for data subjects that may not be of age for validconsent for particular types of personal data to be collected as part ofthe particular transaction. For example, guardians may access theelectronic registry to identify one or more data subjects for which theyare a guardian. Additionally, the guardian may identify one or moretypes of personal data and transactions for which the guardian willprovide guardian consent. Further, in some implementations, the systemmay use previous authorizations of guardian consent between a guardianand particular data subject to identify the guardian of the particulardata subject, and the guardian-data subject link may be created in theelectronic registry of the system.

The system may further be configured to confirm an age of the individual(e.g., parent or guardian) providing consent on the data subject'sbehalf. The system may confirm the individuals age using any suitableage verification technique described herein.

In response to receiving valid consent from the data subject, the systemis configured to transmit the unique transaction ID and the uniqueconsent receipt key back to the third-party consent receipt managementsystem for processing and/or storage. In other embodiments, the systemis configured to transmit the transaction ID to a data store associatedwith one or more entity systems (e.g., for a particular entity on behalfof whom the third-party consent receipt management system is obtainingand managing validly received consent). The system may be furtherconfigured to transmit a consent receipt to the data subject which mayinclude, for example: (1) the unique transaction ID; (2) the uniqueconsent receipt key; and/or (3) any other suitable data related to thevalidly provided consent.

Consent Sharing—WebView and Native Applications

In particular embodiments, any entity (e.g., organization, company,etc.) that collects, stores, processes, etc. personal data may requireone or more of: (1) consent from a data subject from whom the personaldata is collected and/or processed; and/or (2) a lawful basis for thecollection and/or processing of the personal data. In variousembodiments, the entity may be required to, for example: (1) demonstratethat a data subject has freely given specific, informed, and unambiguousindication of the data subject's agreement to the processing of his orher personal data (e.g., in the form of a statement or clear affirmativeaction); (2) demonstrate that the entity received consent from a datasubject in a manner clearly distinguishable from other matters (e.g., inan intelligible and easily accessible form, using clear and plainlanguage, etc.); (3) enable a data subject to withdraw consent as easilyas the data subject can give consent; (4) separate a data subject'sconsent from performance under any contract unless such processing isnecessary for performance under the contract; etc.

In particular, when storing or retrieving information from an end user'sdevice, an entity may be required to receive consent from the end userfor such storage and retrieval. Web cookies are a common technology thatmay be directly impacted by the consent requirements discussed herein.Accordingly, an entity that use cookies (e.g., on one or more webpages)may be required to use one or more banners, pop-ups or other userinterfaces on the website in order to capture consent from end-users tostore and retrieve cookie data.

The consent required to store and retrieve cookie data may, for example,require a clear affirmative act establishing a freely given, specific,informed and unambiguous indication of a data subject's agreement to theprocessing of personal data. This may include, ticking a box whenvisiting an internet website, choosing technical settings forinformation society services, or any other suitable statement or conductwhich clearly indicates in this context the data subject's acceptance ofthe proposed processing of their personal data.

In various embodiments, pre-ticked boxes (or other preselected options)or inactivity may not be sufficient to demonstrate freely given consent.For example, an entity may be unable to rely on implied consent (e.g.,“by visiting this website, you accept cookies”). Without a genuine andfree choice by data subjects and/or other end users, an entity may beunable to demonstrate valid consent (e.g., and therefore unable toutilize cookies in association with such data subjects and/or endusers).

A particular entity may use cookies for any number of suitable reasons.For example, an entity may utilize: (1) one or more functionalitycookies (which may, for example, enhance the functionality of a websiteby storing user preferences such as location for a weather or newswebsite); (2) one or more performance cookies (which may, for example,help to improve performance of the website on the user's device toprovide a better user experience); (3) one or more targeting cookies(which may, for example, be used by advertising partners to build aprofile of interests for a user in order to show relevant advertisementsthrough the website; (4) etc. Cookies may also be used for any othersuitable reason such as, for example: (1) to measure and improve sitequality through analysis of visitor behavior (e.g., through‘analytics’); (2) to personalize pages and remember visitor preferences;(3) to manage shopping carts in online stores; (4) to track peopleacross websites and deliver targeted advertising; (5) etc.

Under various regulations, an entity may not be required to obtainconsent to use every type of cookie utilized by a particular website.For example, strictly necessary cookies, which may include cookies thatare necessary for a website to function, may not require consent. Anexample of strictly necessary cookies may include, for example, sessioncookies. Session cookies may include cookies that are strictly requiredfor website functionality and don't track user activity once the browserwindow is closed. Examples of session cookies include: (1) facetedsearch filter cookies; (2) user authentication cookies; (3) cookies thatenable shopping cart functionality; (4) cookies used to enable playbackof multimedia content; (5) etc.

Cookies which may trigger a requirement for obtaining consent mayinclude cookies such as persistent cookies. Persistent cookies mayinclude, for example, cookies used to track user behavior even after theuse has moved on from a website or closed a browser window.

In order to comply with particular regulations, an entity may berequired to: (1) present visitors with information about the cookies awebsite uses and the purpose of the cookies (e.g., any suitable purposedescribed herein or other suitable purpose); (2) obtain consent to usethose cookies (e.g., obtain separate consent to use each particular typeof cookies used by the website); and (3) provide a mechanism forvisitors to withdraw consent (e.g., that is as straightforward as themechanism through which the visitors initially provided consent). In anyembodiment described herein, an entity may only need to receive validconsent from any particular visitor a single time (e.g., returningvisitors may not be required to provide consent on subsequent visits tothe site). In particular embodiments, although they may not requireexplicit consent to use, an entity may be required to notify a visitorof any strictly necessary cookies used by a website.

In particular embodiments, it may be desirable to share a previouslyprovided consent between a mobile application and one or more WebViewsutilized within the mobile (e.g., or other) software application. Forexample, in various embodiments, a native application (e.g., a nativeapplication used on a particular computing device, such as a mobilecomputing device) may open a WebView within the native application todisplay any suitable information within the WebView. In particularembodiments, a WebView may include, for example, an embeddable browserthat a native application can use to display web content. In particularembodiments, a native application may include any application written ina language and UI framework designed specifically for a particularplatform. In various embodiments, an embeddable browser may include, forexample, any suitable browser engine configured to insert web contentinto a native application and programmatically instruct the nativeapplication on what web content to load within the WebView. In anyembodiment described herein, a WebView may include any visualcomponent/control widget, etc. that may be utilized in composing one ormore visual aspects of a native application. As such, in particularembodiments, a WebView may be at least partially incorporated into anative UI of a native app, which may, for example, be viewed as a userof a native application as another aspect of the native application userinterface.

In particular embodiments, a website being opened in a WebView mayinclude one or more cookie banners (e.g., as described herein) in orderto capture consent for the use of one or more cookies by the websiteopened in the WebView. In various embodiments, one or more cookiespassed within a WebView may not pass to and/or otherwise persist in adefault browser on the device on which the native application isrunning. In various embodiments, the cookie generated and stored by theWebView may be containerized within the WebView. In still otherembodiments, one or more cookies may not be shared between multipleinstances and/or different WebViews initiated within the nativeapplication. In still other embodiments, one or more consents providedwithin the native application may not automatically pass (e.g., via oneor more cookies or other mechanisms) to a WebView launched within thenative application. In some embodiments, this ma, for example, result ina less than seamless user experience in that a user may be required tocomplete two or more consent workflows while using a single nativeapplication (e.g., within both the native application and separately inany WebView launched within the native application).

In a particular example, a user may initially provide consent forparticular data processing during an on-boarding process within a nativeapplication (e.g., when first accessing the native application, whencreating an account for sue with the native application, etc.). In someembodiments, the native application may utilize one or more WebViews inwhich the user has to re-provide consent for the same processing (e.g.,because the consent is not passed from the native application to theWebView). For example, a user accessing a news native application mayinitially register an account with the news agency. When accessingparticular articles within the news agency, the native application maylaunch a WebView that displays a webpage on the news agency's websitethat contains the article. In some embodiments, it may be desirable toavoid requiring the user to consent to any data processing a second time(e.g., or view a consent banner) upon an initial launch of the WebView(e.g., by passing the user's consent from the native application to theWebView).

In particular embodiments, as described herein, any entity (e.g.,organization, company, etc.) that collects, stores, processes, etc.personal data may require consent from a data subject from whom thepersonal data is collected and/or processed. In various embodiments, theentity may be required to, for example, demonstrate that a data subjecthas freely given specific, informed, and unambiguous indication of thedata subject's agreement to the processing of his or her personal datafor one or more specific purposes (e.g., in the form of a statement orclear affirmative action). In various embodiments, the system isconfigured to provide a third-party data repository system to facilitatethe receipt and centralized storage of personal data for each of aplurality of respective data subjects, as described herein.Additionally, the third-party data repository system may be configuredto interface with a centralized consent receipt management system.

In various embodiments, an entity may provide a WebView where atransaction between an entity and a data subject may be performed. TheWebView may be accessible through a web browser (e.g., Chrome, Firefox,Internet Explorer, etc.). As described herein, the transaction mayinvolve the collection or processing of personal data associated withthe data subject by the entity as part of a processing activityundertaken by the entity that the data subject is consenting to as partof the transaction. Additionally, the entity may provide a nativeapplication where the transactions between the entity and a data subjectmay be performed. In some embodiments, the system may be configured toshare consent data between the WebViews and the native application sodata subjects experience a seamless transition while using the eitherthe WebView or the native application, and the data subjects are notrequired to go through a consent workflow for each of the WebView andthe native application.

In various embodiments, the data subject may provide a request toinitiate a transaction between the entity and the data subject, andconsent data may be required from the data subject to initiate thetransaction. The system may receive data subject consent data providedat the WebView by the data subject. In various embodiments, the systemmay translate the data subject consent data provided at the WebView forprocessing within the native application associated with the entity. Forexample, the consent data may comprise one or more WebView cookies,which may be stored, and a consent data software development kit (SDK)may be used to execute a stub or JavaScript function to return one ormore values of one or more WebView cookies. In some embodiments, thesystem may electronically provide the translated data subject consentdata for processing within the native application associated with theentity. Based on the example above, the values of the one or moreWebView cookies may be used by the consent data SDK to provide theconsent data to the native application for processing and storing.Additionally, in some embodiments, the system may electronically providethe data subject consent data to the consent receipt management systemfor processing, as described herein.

In various embodiments, an entity may provide a native application wherethe transaction between the entity and the data subject may beperformed. The system may translate the data subject consent dataprovided at the native application for storage in a storage locationaccessible by a WebView associated with the entity. For example, thesystem may create one or more consent data cookies based on the consentdata provided at the native application, and the system may provide thecreated one or more cookies to a storage location that is accessible bythe WebView for processing. Additionally, in some embodiments, thesystem may electronically provide the data subject consent data to theconsent receipt management system for processing, as described herein.

The system may comprise, for example: (1) receiving, by one or moreprocessors, data subject consent data provided at a WebView associatedwith an entity; (2) translating, by one or more processors, the datasubject consent data provided at the WebView associated with the entityfor processing within the native application associated with the entity;(3) electronically providing, by one or more processors, the translateddata subject consent data for processing within the native applicationassociated with the entity; and (4) electronically providing, by one ormore processors, the data subject consent data to the consent receiptmanagement system for processing.

In some embodiments, the system may comprise, for example: (1)receiving, by one or more processors, data subject consent data providedat a native application associated with an entity; (2) translating, byone or more processors, the data subject consent data provided at thenative application associated with the entity for storage in a storagelocation accessible by a WebView associated with the entity; (3)electronically providing, by one or more processors, the translated datasubject consent data to the storage location accessible by the WebViewassociated with the entity for processing within the WebView associatedwith the entity; and (4) electronically providing, by one or moreprocessors, the data subject consent data to the consent receiptmanagement system for processing.

Native Application Data Processing Consent Sharing Module and RelatedMethods

In particular embodiments, any entity (e.g., organization, company,etc.) that collects, stores, processes, etc. personal data may requireconsent from a data subject from whom the personal data is collectedand/or processed. In various embodiments, the entity may be required to,for example, demonstrate that a data subject has freely given specific,informed, and unambiguous indication of the data subject's agreement tothe processing of his or her personal data for one or more specificpurposes (e.g., in the form of a statement or clear affirmative action).The system may generate and manage a consent receipt under one or moretransactions for a data subject. In some implementations, the system mayrecord consent notice information as a part of the consent receipt. Forexample, the generated consent receipt may include information relatedto whether a data subject that is giving consent for purposes ofprocessing personal data associated with the data subject was shown anotice (e.g., a privacy policy) about the processing of the personaldata associated with the data subject. In some embodiments, the systemmay be configured to store one or more indications consent in anysuitable manner (e.g., using one or more cookies) in order to enable auser to provide consent a single time, and enable the system to accessthe consent in order to continue the consented-to data processingwithout having to re-prompt the user.

Various aspects of the system's functionality may be executed by certainsystem modules, including a Native Application Data Processing ConsentSharing Module 8700. Although this and other modules described hereinare presented as a series of steps, it should be understood in light ofthis disclosure that various embodiments of the Native Application DataProcessing Consent Sharing Module 8700 described herein may perform thesteps described below in an order other than in which they arepresented. In still other embodiments, the Native Application DataProcessing Consent Sharing Module 8700 may omit certain steps describedbelow. In various embodiments, the Native Application Data ProcessingConsent Sharing Module 8700 may perform steps in addition to thosedescribed (e.g., such as one or more steps described with respect to oneor more other modules, etc.). Various embodiments of the system aredescribed more fully below.

In particular embodiments, the Native Application Data ProcessingConsent Sharing Module 8700 is configured for: (1) receiving, by one ormore processors, data subject consent data provided at a WebViewassociated with an entity (e.g., within a native application); (2)translating, by one or more processors, the data subject consent dataprovided at the WebView associated with the entity for processing withinthe native application associated with the entity; (3) electronicallyproviding, by one or more processors, the translated data subjectconsent data for processing within the native application associatedwith the entity; and (4) electronically providing, by one or moreprocessors, the data subject consent data to the consent receiptmanagement system for processing. In still other embodiments, the systemmay be configured to receive data subject consent from within a nativeapplication, translate the data subject consent for processing by aWebView within the native application, and electronically providing thetranslated data subject consent from the native application to theWebView.

In particular embodiments, when executing the Native Application DataProcessing Consent Sharing Module 8700, the system begins, at Step8710A, by receiving, by one or more processors, data subject consentdata provided at a WebView associated with an entity (e.g., within anative application).

Continuing to Step 8720A, the system is configured for translating, byone or more processors, the data subject consent data provided at theWebView associated with the entity for processing within the nativeapplication associated with the entity.

Next, at Step 8730A, the system is configured to electronically provide,by one or more processors, the translated data subject consent data forprocessing within the native application associated with the entity.

Optionally, at Step 8740A, the system may be configured toelectronically provide, by one or more processors, the data subjectconsent data to the consent receipt management system for processing.

In particular embodiments, when executing the Native Application DataProcessing Consent Sharing Module 8700B according to yet anotherembodiment, the system begins, at Step 8710B, by receiving, by one ormore processors, data subject consent data provided at a nativeapplication.

Continuing to Step 8720B, the system is configured for translating, byone or more processors, the data subject consent data provided at nativeapplication for processing within a WebView within the nativeapplication.

Next, at Step 8730B, the system is configured to electronically provide,by one or more processors, the translated data subject consent data forprocessing within the WebView.

Optionally, at Step 8740B, the system may be configured toelectronically provide, by one or more processors, the data subjectconsent data to the consent receipt management system for processing.

For example, in various embodiments, as may be understood from thesystem 8800 shown in FIG. 88, when a data accepts one or more cookies ina WebView 8810, the system may be configured to drop a particular cookie(e.g., OptanonConsent cookie) based on one or more cookie preferencesselected by the user. In other embodiments, the system may be configuredto drop one or more cookies (e.g., one or more eupubconsent cookies, ifapplicable) and store the one or more cookies in cookie storage 8815associated with the WebView. In various embodiments, prior to dismissingthe WebView 8810, a third-party SDK 8825 associated with the nativeapplication 8820 (e.g., the native application 8820 displaying theWebView 8810) may, for example, be configured to execute a stub and/orJavaScript or other function to return one or more values of the one ormore cookies from the WebView 8810. In response to identifying the oneor more values, the third-party SDK 8825 may be configured to store oneor more of the values in a native portion of the code (e.g., one or moreuser preference data files associated with the native application 8820(e.g., NSUserDefaults in iOS and/or one or more Android equivalents). Invarious embodiments, the one or more values may be stored locally (e.g.,in Data storage 8827 or app storage 8829). In other embodiments, the oneor more values may be stored in one or more remote servers 8830.

Similarly, in the system 8890 shown in FIG. 89, the system may receiveconsent from a user within the native application 8820 and store theconsent data for access by a WebView. The system may, for example,append data to a header in a URL request in order to cause the WebView(e.g., or other website) to set one or more cookies for the domain beingloaded (e.g., in the WebView).

Overview of Personal Data Receipts

In particular embodiments, any entity (e.g., organization, company,etc.) that collects, stores, processes, etc. personal data may requireone or more of: (1) consent from a data subject from whom the personaldata is collected and/or processed; and/or (2) a lawful basis for thecollection and/or processing of the personal data. In variousembodiments, the entity may be required to, for example, demonstratethat a data subject has freely given specific, informed, and unambiguousindication of the data subject's agreement to the processing of his orher personal data for one or more specific purposes (e.g., in the formof a statement or clear affirmative action). As such, in particularembodiments, an organization may be required to demonstrate a lawfulbasis for each piece of personal data that the organization hascollected, processed, and/or stored. In particular, each piece ofpersonal data that an organization or entity has a lawful basis tocollect and process may be tied to a particular processing activityundertaken by the organization or entity.

A particular organization may undertake a plurality of different privacycampaigns, processing activities, etc. that involve the collection andstorage of personal data. In some embodiments, each of the plurality ofdifferent processing activities may collect redundant data (e.g., maycollect the same personal data for a particular individual more thanonce), and may store data and/or redundant data in one or moreparticular locations (e.g., on one or more different servers, in one ormore different databases, etc.). In this way, because of the number ofprocessing activities that an organization may undertake, and the amountof data collected as part of those processing activities over time, oneor more data systems associated with an entity or organization may storeor continue to store data that is not associated with any particularprocessing activity (e.g., any particular current processing activity).Under various legal and industry standards related to the collection andstorage of personal data, such data may not have or may no longer have alegal basis for the organization or entity to continue to store thedata. As such, organizations and entities may require improved systemsand methods to maintain an inventory of data assets utilized to processand/or store personal data for which a data subject has provided consentfor such storage and/or processing.

In various embodiments, the system is configured to provide athird-party data repository system to facilitate the receipt andcentralized storage of personal data (e.g., and a plurality of personaldata receipts to memorialize a justification for processing particularpersonal data) for each of a plurality of respective data subjects, asdescribed herein. Additionally, the third-party data repository systemis configured to interface with a centralized consent receipt managementsystem.

A triggering action may prompt the system to identify one or more piecesof personal data associated with one or more data subjects, and delete(or modify) all or a portion of the identified one or more pieces ofpersonal data. In some implementations, the particular organization mayreceive a data subject access request that comprises a particularrequest to perform one or more actions with any personal data stored bythe particular organization regarding the requestor. For example, insome embodiments, the request may include a request to view one or morepieces of personal data stored by the system regarding the requestor. Inother embodiments, the request may include a request to delete one ormore pieces of personal data stored by the system regarding therequestor. In still other embodiments, the request may include a requestto update one or more pieces of personal data stored by the systemregarding the requestor. The data subject access request may be providedto the third-party data repository system to identify and locate thepersonal data stored by the particular organization regarding therequestor, as described herein. Further, where consent to collect,store, and/or process particular personal data associated with a datasubject is withdrawn by the data subject

Additionally, in some embodiments, once a privacy campaign is completedby the particular organization, the system may notify a privacy officerassociated with the privacy campaign that the personal data stored bythe particular organization associated with the privacy campaign may nolonger be needed to be stored. Moreover, in some embodiments, whenparticular personal data stored by the particular organization has beenstored for a particular period of time (e.g., based on regulationsdefined in privacy laws) or the particular personal data stored by theparticular organization has not been accessed for a particular period oftime (e.g., a threshold period of time), then the system may notify aprivacy officer that such personal data stored by the particularorganization may no longer be needed to be stored. Further, in someimplementations, the system may initiate deleting the identifiedpersonal data (e.g., personal data associated with an expired privacycampaign, personal data stored for a particular period of time, orpersonal data that has not been accessed for a period of time) stored bythe particular organization.

In response to identifying the personal data, the system may determineif there are one or more legal bases to retain one or more pieces of theidentified personal data. The one or more legal bases may include, forexample, (i) an ongoing legal case where particular personal data is tobe retained, (ii) machine learning data generated by the particularorganization that incorporates one or more pieces of the identifiedpersonal data (e.g., custom settings selected by the data subject,aggregate data collected by the particular organization, etc.), or (iii)any other legal basis to retain one or more pieces of the identifiedpersonal data.

In particular embodiments, the system is configured to generate apersonal data receipt in response to identifying the one or more legalbases for continuing to store the one or more pieces of personal data.In some embodiments, the personal data receipt may, for example, operatein a similar manner to various embodiments of a consent receiptdescribed herein. The personal data receipt may, for example,memorialize a basis for continuing to store, process, and otherwisecollect personal data (e.g., for one or more particular data subjects)for one or more reasons other than direct consent from each of the oneor more data subjects. The system may, for example, be configured tolink (e.g., electronically link in computer memory) the generatedpersonal data receipt to: (1) the determined legal basis; (2) the one ormore first pieces of personal data that the system has identified ashaving a legal basis for continuing the processing/storage/collectionof; (3) one or more processing activities associated with the personaldata; (4) a unique identifier associated with the particular datasubject; and/or (5) any other suitable data.

In response, the system may retain the one or more pieces of theidentified personal data that have a legal basis for retention anddelete the remaining one or more pieces of the identified personal datathat do not have a legal basis for retention. In some embodiments, thesystem may identify a first set of one or more pieces of the identifiedpersonal data that have a legal basis for retention and a second set ofone or more pieces of the identified personal data that do not have alegal basis for retention. In some implementations, the system mayautomatically retain the one or more pieces of the identified personaldata that have a legal basis for retention and delete the remaining oneor more pieces of the identified personal data that do not have a legalbasis for retention. In some implementations, the system may provide theone or more pieces of the identified personal data that have a legalbasis for retention to one or more privacy officers to review and verifythere is a legal basis for retention, and the one or more privacyofficer may select to retain a portion or all of the one or more piecesof the identified personal data that have a legal basis for retention. Anotification may be provided to particular parties, for example, one ormore privacy officers or the data subject, to indicate the actionperformed (e.g., which data of the identified personal data have a legalbasis for retention, the data of the identified personal data that wasretained and/or deleted).

In some embodiments, the system may be configured to generate and storea personal data receipt for each incidence of consent (e.g., to theprocessing of one or more pieces of personal data) captured by thesystem as well as each incidence of an identification of a basis for theprocessing of the data other than consent received from the datasubject. The system may, for example, be configured to transmit thepersonal data receipt (e.g., or In such embodiments, the system may beconfigured, for example to enable a data subject to use the personaldata receipt in the exercise of one or more rights (e.g., one or morerights related to the processing, collection, and/or storage of personaldata describe herein). For example, in response to a user providingconsent to the processing of one or more pieces of personal data, thesystem may be configured to: (1) generate a personal data receipt thatstores data related to the provided consent; and (2) provide a copy ofthe personal data receipt to the data subject. In some embodiments, thesystem is configured to receive the copy of the personal data receipt inresponse to a request, from the data subject, to exercise one or moredata subject's rights described herein. In various embodiments, thesystem is configured to use the personal data receipt to verify anidentify of the holder of the receipt as the individual to whom thepersonal data receipt was issued (e.g., the data subject).

Personal Data Receipt Module and Related Methods

As may be understood in light of this disclosure, a particularorganization may undertake a plurality of different privacy campaigns,processing activities, etc. that involve the collection and storage ofpersonal data. In various embodiments, the system may be configured foridentifying one or more pieces of personal data associated with a datasubject, identifying a storage location of each of the one or morepieces of personal data associated with the data subject, analyzing anddetermining that a first portion of the one or more of the pieces ofpersonal data has one or more legal bases for continued storage andautomatically maintaining storage of the first portion of the one ormore pieces of personal data, and automatically facilitating deletion ofa second portion of the one or more pieces of personal data associatedwith the data subject, wherein the second portion of the one or morepieces of personal data associated with the data subject is differentfrom the first portion of the one or more pieces of personal data.

Various aspects of the system's functionality may be executed by certainsystem modules, including a Personal Data Receipt Module 9000. Althoughthese modules are presented as a series of steps, it should beunderstood in light of this disclosure that various embodiments of thePersonal Data Receipt Module 9000 described herein may perform the stepsdescribed below in an order other than in which they are presented. Instill other embodiments, the Personal Data Receipt Module 9000 may omitcertain steps described below. In various embodiments, the Personal DataReceipt Module 9000 may perform steps in addition to those described(e.g., such as one or more steps described with respect to one or moreother modules, etc.). Various embodiments of the system are describedmore fully below.

In particular embodiments, a Personal Data Receipt Module 9000 isconfigured for (1) identifying one or more pieces of personal dataassociated with a data subject based at least in part on one or moretriggering action; (2) identifying a storage location of each of the oneor more pieces of personal data associated with the data subject; (3) inresponse to identifying the storage location of each of the one or morepieces of personal data associated with the data subject, automaticallydetermining that a first portion of the one or more of the pieces ofpersonal data has one or more legal bases for continued storage; (4) inresponse to determining that the first portion of the one or more of thepieces of personal data associated with the data subject has one or morelegal bases for continued storage, automatically maintaining storage ofthe first portion of the one or more pieces of personal data; and (5)automatically facilitating deletion of a second portion of the one ormore pieces of personal data associated with the data subject, whereinthe second portion of the one or more pieces of personal data associatedwith the data subject is different from the first portion of the one ormore pieces of personal data.

As may be understood from FIG. 90, when executing the Personal DataReceipt Module 9000, the system begins, at Step 9010, by identifying oneor more pieces of personal data associated with a data subject based atleast in part on one or more triggering actions. For example, in variousembodiments, the system is configured to identify any personal datastored in any database, server, or other data repository associated witha particular organization. In various embodiments, the system isconfigured to use one or more data models, such as those describedabove, to identify this personal data and suitable related information(e.g., where the personal data is stored, who has access to the personaldata, etc.). In various embodiments, the system is configured to useintelligent identity scanning (e.g., as described above) to identify therequestor's personal data and related information that is to be used tofulfill the request.

In still other embodiments, the system is configured to use one or moremachine learning techniques to identify such personal data. For example,the system may identify particular stored personal data based on, forexample, a country in which a website that the data subject request wassubmitted is based, or any other suitable information.

In particular embodiments, the system is configured to scan and/orsearch one or more existing data models (e.g., one or more current datamodels) in response to receiving the request in order to identify theone or more pieces of personal data associated with the requestor. Thesystem may, for example, identify, based on one or more data inventories(e.g., one or more inventory attributes) a plurality of storagelocations that store personal data associated with the requestor. Inother embodiments, the system may be configured to generate a data modelor perform one or more scanning techniques in response to receiving therequest (e.g., in order to automatically fulfill the request).

In various embodiments, the one or more triggering action may be a datasubject access request, which comprises a particular request to performone or more actions with any personal data stored by a particularorganization regarding the data subject. For example, in someembodiments, the request may include a request to view one or morepieces of personal data stored by the system regarding the requestor. Inother embodiments, the request may include a request to delete one ormore pieces of personal data stored by the system regarding therequestor. In still other embodiments, the request may include a requestto update one or more pieces of personal data stored by the systemregarding the requestor. In still other embodiments, the request mayinclude a request based on any suitable right afforded to a datasubject, such as those discussed above.

As described herein, in various embodiments, an organization,corporation, etc. may be required to provide information requested by anindividual for whom the organization stores personal data within acertain time period (e.g., 30 days). As a particular example, anorganization may be required to provide an individual with a listing of,for example: (1) any personal data that the organization is processingfor an individual, (2) an explanation of the categories of data beingprocessed and the purpose of such processing; and/or (3) categories ofthird parties to whom the data may be disclosed. Various privacy andsecurity policies (e.g., such as the European Union's General DataProtection Regulation, and other such policies) may provide datasubjects (e.g., individuals, organizations, or other entities) withcertain rights related to the data subject's personal data that iscollected, stored, or otherwise processed by an organization.

Continuing to Step 9020, the system is configured to identify a storagelocation of each of the one or more pieces of personal data associatedwith the data subject. The system may, for example, be configured toconnect to one or more databases associated with a particularorganization (e.g., one or more databases that may serve as a storagelocation for any personal or other data collected, processed, etc. bythe particular organization, for example, as part of a suitableprocessing activity. As may be understood in light of this disclosure, aparticular organization may use a plurality of one or more databases, aplurality of servers, or any other suitable data storage location inorder to store personal data and other data collected.

Next, at Step 9030, in response to identifying the storage location ofeach of the one or more pieces of personal data associated with the datasubject, the system is configured for, automatically determining that afirst portion of the one or more of the pieces of personal data has oneor more legal bases for continued storage. The system may determine ifthere are one or more legal bases to retain one or more pieces of theidentified personal data, which may be a first portion of personal data.The one or more legal bases may include, for example, (i) an ongoinglegal case where particular personal data is to be retained, (ii)machine learning data generated by the particular organization thatincorporates one or more pieces of the identified personal data (e.g.,custom settings selected by the data subject, aggregate data collectedby the particular organization, etc.), (iii) consent from the datasubject for the continued storage of the one or more pieces of personaldata, (iv) an indication provided by the organization that the one ormore pieces of personal data are a part of anonymized data (e.g.,aggregate data collected by the particular organization, etc.), or (v)any other legal basis to retain one or more pieces of the identifiedpersonal data.

Further, in various embodiments, the system may provide the firstportion of the one or more of the pieces of personal data associatedwith the data subject has one or more legal bases for continued storageto one or more privacy officers of the organization, and the system may,in response, receive storage retention feedback from the one or moreprivacy officers associated with the first portion of the one or more ofthe pieces of personal data associated with the data subject. Thestorage retention feedback may include a selection of a first set of thefirst portion of the one or more pieces of personal data for which tomaintain continued storage. For example, the one or more privacyofficers may determine that a part of the first portion of the one ormore pieces of personal data actually has a legal basis for retention;however, a second set of the first portion of the one or more pieces ofpersonal data may not have a legal basis for retention (e.g., it may betoo risky for the organization to retain that set of data).

At Step 9040, in response to determining that the first portion of theone or more of the pieces of personal data associated with the datasubject has one or more legal bases for continued storage, the system isconfigured for, automatically maintaining storage of the first portionof the one or more pieces of personal data. In some implementations, thesystem may automatically retain the one or more pieces of the identifiedpersonal data that have a legal basis for retention and delete theremaining one or more pieces of the identified personal data that do nothave a legal basis for retention.

In various embodiments, the system may apply one or more storageattributes to the first portion of the one or more pieces of personaldata, and determine whether to maintain storage of the first portion ofthe one or more pieces of personal data based at least in part on theapplying the one or more storage attribute to the first portion of theone or more pieces of personal data. In some implementations, thestorage attribute may include a storage time (e.g., the one or morepieces of personal data have been stored for 30 days) of the one or morepieces of personal data. The system may compare the storage time of theone or more pieces of personal data to an authorized storage time forthe organization to store the one or more pieces of personal data, andin response to determining that the storage time of the one or morepieces of personal data is greater than the authorized storage time forthe organization to store the one or more pieces of personal data,automatically notifying one or more privacy officers. In variousembodiments, in response to determining that the storage time of the oneor more pieces of personal data is greater than the authorized storagetime for the organization to store the one or more pieces of personaldata, automatically facilitating deletion of the first portion of theone or more pieces of personal data associated with the data subject.

In some embodiments, the storage attribute may include a relevancyattribute of the one or more pieces of personal data. The system maydetermine that a privacy campaign associated with the one or more piecesof personal data is inactive. As may be understood in light of thisdisclosure, a particular organization may undertake a plurality ofdifferent privacy campaigns, processing activities, etc. that involvethe collection and storage of personal data. A privacy campaign may beinactive, for example, (1) when the privacy campaign has not beenaccessed by a member of the organization in a set period of time, (2)when the privacy campaign is deleted, (3) etc. In response todetermining that a privacy campaign associated with the one or morepieces of personal data is inactive, the system may automaticallyfacilitate deletion of the first portion of the one or more pieces ofpersonal data associated with the data subject.

In various other embodiments, the system is configured to generate aconsent receipt (e.g., using any suitable technique described herein)and store an indication in association with the consent receiptindicating the determined legal basis for the storage and/or processingof particular data. As such, the system may be configured to maintain arecord of one or more legal bases for processing personal data inaddition to storing consent receipts for explicit consent provided by adata subject as described herein. In this way, the system may beconfigured to maintain a complete record of any determined basis forstoring, collecting, and/or processing particular data (e.g., throughexplicit consent, implicit/implied consent, one or more legal bases,etc.).

Continuing to Step 9050, the system is configured to automaticallyfacilitate deletion of a second portion of the one or more pieces ofpersonal data associated with the data subject, wherein the secondportion of the one or more pieces of personal data associated with thedata subject is different from the first portion of the one or morepieces of personal data. The second portion of the one or more pieces ofpersonal data may be deleted, as it may not have a legal basis forretention. The system may automatically delete the second portion of theone or more pieces of personal data. In some implementations, the systemmay provide the second portion of the one or more pieces of personaldata to one or more privacy officers of the organization to review anddelete the data.

In some implementations, the system may provide the one or more piecesof the identified personal data that have a legal basis for retention toone or more privacy officers to review and verify there is a legal basisfor retention, and the one or more privacy officer may select to retaina portion or all of the one or more pieces of the identified personaldata that have a legal basis for retention. A notification may beprovided to particular parties, for example, one or more privacyofficers or the data subject, to indicate the action performed (e.g.,which data of the identified personal data have a legal basis forretention, the data of the identified personal data that was retainedand/or deleted).

Overview of Personal Data Verification= of Consent

In particular embodiments, any entity (e.g., organization, company,etc.) that collects, stores, processes, etc. personal data may requireconsent from a data subject from whom the personal data is collectedand/or processed. In various embodiments, the entity may be required to,for example, demonstrate that a data subject has freely given specific,informed, and unambiguous indication of the data subject's agreement tothe processing of his or her personal data for one or more specificpurposes (e.g., in the form of a statement or clear affirmative action).In various embodiments, the system is configured to provide athird-party data repository system to facilitate the receipt andcentralized storage of personal data for each of a plurality ofrespective data subjects, as described herein. In particularembodiments, a third-party data repository system is configured tointerface with a consent receipt management system (e.g., such as theconsent receipt management system described below).

The system may be configured to integrate with (e.g., interface with) aconsent receipt management system (e.g., such as the consent receiptmanagement system described more fully below). The system may generateand manage a consent receipt under one or more transactions for a datasubject. In some implementations, the system may record consent noticeinformation as a part of the consent receipt. For example, the generatedconsent receipt may include information related to whether a datasubject that is giving consent for purposes of processing personal dataassociated with the data subject was shown a notice about the processingof the personal data associated with the data subject.

When the data subject provides consent (e.g., on a mobile application ora webform), the system may determine whether there is a privacy policyprovided on the same user interface where the user provided consent or alink to a privacy policy directed to the particular consent the datasubject is providing. The system may, for example, be configured totrack data related to: (1) whether the data subject selected to view theprivacy policy (e.g., whether the data subject select the link to theprivacy policy and/or scrolled to the end of the provided privacypolicy); (2) whether the data subject selected to view the privacypolicy within a determined period of time and/or before another actionwas performed (e.g., whether the user selected to view the privacypolicy before providing consent or within a number of minutes afterbeing presented with the option to view the privacy policy or select thelink to the privacy policy); or (3) etc. The system may include thistracked data in the consent receipt generated by the system.

Additionally, the system may access the privacy policy (e.g., providedon the same user interface where the user provided consent or a link toa privacy policy), and import one or more terms and conditions providedin the privacy policy to the consent receipt. A time stamp may also beprovided with the one or more terms and conditions of the privacypolicy. The consent receipt may then indicate the notice that wasprovided to the data subject when the data subject gave consent based onthe content and/or time stamp associated with the privacy policy. Insome implementations, a link to a stored version of the one or moreterms and conditions of the privacy policy may be provided in theconsent receipt.

The computer-implemented method may be configured for: (1) receiving arequest to initiate a transaction between the entity and the datasubject; (2) providing, at the user interface, a privacy policyassociated with the entity and based at least in part on the request toinitiate the transaction between the entity and the data subject; (3)accessing the privacy policy associated with the entity and based atleast in part on the request to initiate the transaction between theentity and the data subject; (4) storing one or more provision of theprivacy policy associated with the entity and based at least in part onthe request to initiate the transaction between the entity and the datasubject; (5) providing a user interface for consenting to the privacypolicy associated with the entity and based at least in part on therequest to initiate the transaction between the entity and the datasubject; (6) receiving a selection to consent to the privacy policyassociated with the entity and based at least in part on the request toinitiate the transaction between the entity and the data subject; (7) inresponse to the selection, generating, by a third party consent receiptmanagement system, a consent receipt to the data subject, wherein theconsent receipt include the stored one or more provision of the privacypolicy; and (8) storing, by the third party consent receipt managementsystem, the generated consent receipt.

Personal Data Consent Verification Module and Related Methods

In particular embodiments, any entity (e.g., organization, company,etc.) that collects, stores, processes, etc. personal data may requireconsent from a data subject from whom the personal data is collectedand/or processed. In various embodiments, the entity may be required to,for example, demonstrate that a data subject has freely given specific,informed, and unambiguous indication of the data subject's agreement tothe processing of his or her personal data for one or more specificpurposes (e.g., in the form of a statement or clear affirmative action).The system may generate and manage a consent receipt under one or moretransactions for a data subject. In some implementations, the system mayrecord consent notice information as a part of the consent receipt. Forexample, the generated consent receipt may include information relatedto whether a data subject that is giving consent for purposes ofprocessing personal data associated with the data subject was shown anotice (e.g., a privacy policy) about the processing of the personaldata associated with the data subject.

Various aspects of the system's functionality may be executed by certainsystem modules, including a Personal Data Consent Verification Module9100. Although these modules are presented as a series of steps, itshould be understood in light of this disclosure that variousembodiments of the Personal Data Consent Verification Module 9100described herein may perform the steps described below in an order otherthan in which they are presented. In still other embodiments, thePersonal Data Consent Verification Module 9100 may omit certain stepsdescribed below. In various embodiments, the Personal Data ConsentVerification Module 9100 may perform steps in addition to thosedescribed (e.g., such as one or more steps described with respect to oneor more other modules, etc.). Various embodiments of the system aredescribed more fully below.

In particular embodiments, a Personal Data Consent Verification Module9100 is configured for: (1) receiving a request to initiate atransaction between the entity and the data subject; (2) providing, atthe user interface, a privacy policy associated with the entity andbased at least in part on the request to initiate the transactionbetween the entity and the data subject; (3) accessing the privacypolicy associated with the entity and based at least in part on therequest to initiate the transaction between the entity and the datasubject; (4) storing one or more provision of the privacy policyassociated with the entity and based at least in part on the request toinitiate the transaction between the entity and the data subject; (5)providing a user interface for consenting to the privacy policyassociated with the entity and based at least in part on the request toinitiate the transaction between the entity and the data subject; (6)receiving a selection to consent to the privacy policy associated withthe entity and based at least in part on the request to initiate thetransaction between the entity and the data subject; (7) in response tothe selection, generating, by a third party consent receipt managementsystem, a consent receipt to the data subject, wherein the consentreceipt include the stored one or more provision of the privacy policy;and (8) storing, by the third party consent receipt management system,the generated consent receipt.

As may be understood from FIG. 91, when executing the Personal DataReceipt Module 9100, the system begins, at Step 9110, by receiving arequest to initiate a transaction between the entity and the datasubject. In particular embodiments, a third-party consent receiptmanagement system may be configured to manage one or more consentreceipts for a particular entity. As may be understood from this figure,a data subject may access an interaction interface (e.g., via the web)for interacting with a particular entity (e.g., one or more entitysystems). The interaction interface (e.g., user interface) may include,for example, a suitable website, web form, user interface etc. Theinteraction interface may be provided by the entity. Using theinteraction interface, a data subject may initiate a transaction withthe entity that requires the data subject to provide valid consent(e.g., because the transaction includes the processing of personal databy the entity). The transaction may include, for example: (1) accessingthe entity's website; (2) signing up for a user account with the entity;(3) signing up for a mailing list with the entity; (4) a free trial signup; (5) product registration; and/or (6) any other suitable transactionthat may result in collection and/or processing personal data, by theentity, about the data subject.

As may be understood from this disclosure, any particular transactionmay record and/or require one or more valid consents from the datasubject. For example, the system may require a particular data subjectto provide consent for each particular type of personal data that willbe collected as part of the transaction. The system may, in variousembodiments, be configured to prompt the data subject to provide validconsent, for example, by: (1) displaying, via the interaction interface,one or more pieces of information regarding the consent (e.g., whatpersonal data will be collected, how it will be used, etc.); and (2)prompt the data subject to provide the consent.

In response to the data subject (e.g., or the entity) initiating thetransaction, the system may be configured to: (1) generate a uniquereceipt key (e.g., unique receipt ID); (2) associate the unique receiptkey with the data subject (e.g., a unique subject identifier), theentity, and the transaction; and (3) electronically store (e.g., incomputer memory) the unique receipt key. The system may further store aunique user ID (e.g., unique subject identifier) associated with thedata subject (e.g., a hashed user ID, a unique user ID provided by thedata subject, unique ID based on a piece of personal data such as ane-mail address, etc.).

Continuing to Step 9120, the system is configured for providing, at theuser interface, a privacy policy associated with the entity and based atleast in part on the request to initiate the transaction between theentity and the data subject. The privacy policy may be configured forthe particular transaction to notify the data subject of, for example,(1) what type of personal data is to be collected, (2) how long thepersonal data will be stored, (3) storage features of the personal data(e.g., encrypted), (4) the purpose of collecting the personal data, (5)rights of the data subject regarding data collection, (6) etc. Thesystem may include one or more electronic links to the privacy policystored on one or more data assets of the entity and associated with thetransaction

Next, at Step 9130, the system is configured for accessing the privacypolicy associated with the entity and based at least in part on therequest to initiate the transaction between the entity and the datasubject. The system may access the privacy policy stored within one ormore data assets of the entity. At Step 9140, the system is configuredfor storing one or more provision of the privacy policy associated withthe entity and based at least in part on the request to initiate thetransaction between the entity and the data subject. The system mayaccess the privacy policy (e.g., provided on the same user interfacewhere the user provided consent or a link to a privacy policy), andimport one or more terms and conditions provided in the privacy policyto the consent receipt.

A time stamp may also be provided with the one or more terms andconditions of the privacy policy. The consent receipt may then indicatethe notice that was provided to the data subject when the data subjectgave consent based on the content and/or time stamp associated with theprivacy policy. In some implementations, a link to a stored version ofthe one or more terms and conditions of the privacy policy may beprovided in the consent receipt.

Continuing to Step 9150, the system is configured to provide a userinterface for consenting to the privacy policy associated with theentity and based at least in part on the request to initiate thetransaction between the entity and the data subject. The system maytrack the data subject's interaction with the user interface forconsenting to the privacy policy. The system may, for example, beconfigured to track data related to: (1) whether the data subjectselected to view the privacy policy (e.g., whether the data subjectselect the link to the privacy policy and/or scrolled to the end of theprovided privacy policy); (2) whether the data subject selected to viewthe privacy policy within a determined period of time and/or beforeanother action was performed (e.g., whether the user selected to viewthe privacy policy before providing consent or within a number ofminutes after being presented with the option to view the privacy policyor select the link to the privacy policy); or (3) etc. The system mayinclude this tracked data in the consent receipt generated by thesystem.

In some implementations, the system may be configured to capture one ormore pieces of interaction data based at least in part on the datasubject's interaction with the user interface for consenting to theprivacy policy, and store the interaction data with the generatedconsent receipt. The interaction data may include, for example, (i) anindication of whether the data subject selected to view the privacypolicy (e.g., whether the data subject selected one or more pixels ofthe user interface for consenting to the privacy policy associated withviewing the privacy policy), or (ii) an indication of whether the datasubject scrolled to the end of the privacy policy. Further, in someimplementations, the interaction data may include tracking how long ittakes for the user to select to view the privacy policy. For example,the system may track a period of time between (i) a first time that thedata subject is presented with the user interface for consenting to theprivacy policy and (ii) a second time that the data subject selected oneor more pixels of the user interface for consenting to the privacypolicy associated with viewing the privacy policy. Further, theinteraction data may include tracking a number of interactions the datasubject has with the user interface before selecting to view the privacypolicy. For example, the system may track a number of data subjectinteractions with the user interface for consenting to the privacypolicy between (i) a first time that the data subject is presented withthe user interface for consenting to the privacy policy and (ii) asecond time that the data subject selected one or more pixels of theuser interface for consenting to the privacy policy associated withviewing the privacy policy.

At Step 9160, the system may be configured for receiving a selection toconsent to the privacy policy associated with the entity and based atleast in part on the request to initiate the transaction between theentity and the data subject. The system may, for example, be configuredto track data on behalf of an entity that collects and/or processespersonal data related to: (1) who consented to the processing orcollection of personal data (e.g., the data subject themselves or aperson legally entitled to consent on their behalf such as a parent,guardian, etc.); (2) when the consent was given (e.g., a date and time);(3) what information was provided to the consenter at the time ofconsent (e.g., a privacy policy, what personal data would be collectedfollowing the provision of the consent, for what purpose that personaldata would be collected, etc.); (4) how consent was received (e.g., oneor more copies of a data capture form, web form, etc. via which consentwas provided by the consenter); (5) when consent was withdrawn (e.g., adate and time of consent withdrawal if the consenter withdraws consent);and/or (6) any other suitable data related to receipt or withdrawal ofconsent. In particular embodiments, the system is configured to storemetadata in association with processed personal data that indicates oneor more pieces of consent data that authorized the processing of thepersonal data.

At Step 9170, in response to the selection, the system may generate, bya third-party consent receipt management system, a consent receipt tothe data subject, wherein the consent receipt includes the stored one ormore provisions of the privacy policy. In various embodiment describedherein, the system may be configured to generate a consent receipt inresponse to a data subject providing valid consent. In variousembodiments, a consent receipt management system is configured togenerate a consent receipt for a data subject that links to (e.g., incomputer memory) metadata identifying a particular purpose of thecollection and/or processing of personal data that the data subjectconsented to, a capture point of the consent (e.g., a copy of the webform or other mechanism through which the data subject provided consent,and other data associated with one or more ways in which the datasubject granted consent. The consent receipt may include the stored oneor more provisions of the privacy policy. Further, at Step 9180, thesystem is configured to store, by the third-party consent receiptmanagement system, the generated consent receipt. In particularembodiments, a third party consent receipt management system may beconfigured to manage one or more consent receipts for a particularentity.

Automatically Generating Consent Interfaces

In particular embodiments, any entity (e.g., organization, company,etc.) that collects, stores, processes, etc. personal data may requireconsent from a data subject from whom the personal data is collectedand/or processed. In various embodiments, the entity may be required to,for example, demonstrate that a data subject has freely given specific,informed, and unambiguous indication of the data subject's agreement tothe processing of his or her personal data for one or more specificpurposes (e.g., in the form of a statement or clear affirmative action).In various embodiments, the system is configured to provide athird-party data repository system to facilitate the receipt andcentralized storage of personal data for each of a plurality ofrespective data subjects, as described herein. In particularembodiments, a third party data repository system is configured tointerface with a consent receipt management system (e.g., such as theconsent receipt management system described below).

In particular embodiments, a data subject may encounter a user interfaceto complete that may be a webform or application interface. The userinterface may be an interface for the data subject to provide consent tothe processing of personal data. In some implementations, the datasubject may provide particular personal data (e.g., first and last name,email, company, job title, phone number, etc.) in the webform orapplication interface. The system may generate the user interface forconsent based on particular user interface attributes (e.g., datasubject name, payment information, etc.) necessary for each particularprivacy campaign or type of privacy campaign. In some implementations,the user interface for consent may be generated to limit, or otherwisereduce, the number of selections and/or text inputs required by the datasubject, which, for example, may minimize the user interaction requiredby the user interface for consent and optimize the opt-in rate.Additionally, the user interface for consent may be generated based onthe attribute of data privacy laws (e.g., key factors of data privacylaws such as explicit opt-in, equal weighting of options, granularconsent, etc.) pertaining to the particular personal data collectedwithin the webform or application interface and/or by the privacycampaign.

In some implementations, the system may automatically generate the userinterface for consent that is presented within the webform orapplication interface. In some implementations, one or more userinterfaces for consent are generated, and then presented to one or moreprivacy officer for selection, where the selected user interface forconsent is then presented within the webform or application interface.Additionally, in some implementations, the system may be enabled toaccess one or more pieces of information required to be provided in theuser interfaces for consent by the data subject. For example, the datasubject may have previously provided the one or more pieces ofinformation (e.g., in a different user interface for consent associatedwith the particular organization) to the system of the particularorganization, and the system can identify the data subject and accessany one or more pieces of personal information the system has stored forthe data subject. Additionally, the data subject's computing device(e.g., smart phone, laptop, tablet, etc.) and/or initiated web browseror software application may include an auto-fill option that is enabled(e.g., the data subject's name set to auto-fill in the user interfacefor consent).

FIG. 40 provides an example user interface for consent 4000 that thesystem may generate. The system may identify, or otherwise select (e.g.,automatically), the particular user interface for consent 4000 tominimize the user interaction required but also include the necessaryuser interaction required based on particular data privacy lawspertaining to the particular personal data collected within the webformor application interface and/or by the privacy campaign. In someimplementations, the user interface for consent 4000 may beautomatically presented within the webform or application interface. Insome implementations, the user interface for consent 4000 may bepresented to one or more privacy officer, and then be selected as theuser interface for consent is then presented within the webform orapplication interface.

FIG. 40 provides an example user interface for consent where a datasubject (e.g., John Doe) may provide particular personal data (e.g.,first and last name, email, company, job title, phone number, etc.) whensigning up for a free trial with a particular entity via a trial signupinterface 4000. The system may be enabled to access one or more piecesof information required to be provided in the user interfaces forconsent by the data subject, and automatically complete, or otherwisefill out, one or more portions of the user interface for consent (e.g.,fill out the name John Doe based on the data subject, John Doe,previously completing a user interface for consent associated with adifferent privacy campaign of the same particular organization). As maybe understood in light of this disclosure, the free trial may constitutea transaction between the data subject (e.g., user) and a particularentity providing the free trial. In various embodiments, the datasubject (e.g., user) may encounter the interface shown in FIG. 40 inresponse to accessing a website associated with the particular entityfor the free trial (e.g., a sign up page).

The computer-implemented method may be configured for: (1) receiving arequest to initiate a transaction between an entity and a data subject;(2) determining one or more user interface attributes based at least inpart on the transaction between the entity and the data subject; (3)generating a user interface for consent based at least in part on theone or more user interface attributes and one or more user interfaceselections; and (4) providing the user interface for consent to the datasubject for completion.

In various embodiments, the system may be configured to automaticallygenerate a user interface for providing consent (e.g., consent for theprocessing of one or more pieces of personal data, personallyidentifiable data, etc.). In particular, the system may be configured togenerate the interface based on, for example: (1) one or more privacylaws that apply to the processing of the data (e.g., based on a locationof a user providing the consent); (2) one or more weighting optionsrelated to the processing; (3) a type of consent required; (4) etc. Insome embodiments, the system may be configured to minimize thecomplexity of the user interface (e.g., by generating a user interfacethat includes the least number of necessary interface elements that areexplicitly necessary to comply with one or more prevailing laws,regulations, and/or best practices. For example, the system may beconfigured to store and maintain a data store of user interfaceelements, each of which correspond to one or more consent collectionrequirements. The system may then automatically generate a consentinterface that includes one or more of the elements based on one or morerules and/or regulations that apply to a particular processing activityfor which the system requires some form of consent. These rules maydiffer, for example, based at least in part on a location of the user, alocation of the entity, etc. For example, a first user accessing awebsite form a first country may encounter a different system-generatedinterface than a second visitor accessing the site from a second country(e.g., because one or more consent laws different between the first andsecond country). In particular embodiments, the system may be configuredto generate the user interface in response to the user accessing aparticular webpage for which the system may need to collect consent(e.g., consent to the user of one or more cookies by the particularwebpage).

Overview of Cookie Compliance Testing with Website Scanning

In particular embodiments, any entity (e.g., organization, company,etc.) that collects, stores, processes, etc. personal data may requireconsent from a data subject from whom the personal data is collectedand/or processed. In various embodiments, the entity may be required to,for example, demonstrate that a data subject has freely given specific,informed, and unambiguous indication of the data subject's agreement tothe processing of his or her personal data for one or more specificpurposes (e.g., in the form of a statement or clear affirmative action).In various embodiments, the system is configured to provide athird-party data repository system to facilitate the receipt andcentralized storage of personal data for each of a plurality ofrespective data subjects, as described herein. In particularembodiments, a third-party data repository system is configured tointerface with a consent receipt management system (e.g., such as theconsent receipt management system described below).

Using an interaction interface, a data subject may initiate aninteraction with the entity that requires the data subject to providevalid consent (e.g., the interaction involving a transaction thatincludes the processing of personal data by the entity). The interactionmay include, for example: (1) interacting with the entity's website(e.g., which may utilize one or more cookies and/or other trackingtechnologies to monitor the data subject's activity while accessing thewebsite or other websites; enable certain functionality on one or morepages of the entity's website, such as location services; etc.); (2)signing up for a user account with the entity; (3) signing up for amailing list with the entity; (4) a free trial sign up; (5) productregistration; and/or (6) any other suitable interaction that may resultin collection and/or processing of personal data, by the entity, aboutthe data subject.

In various embodiments, a website scanning tool may be used to determinea website category of the website (e.g., whether personal data is beingused with any presentation provided in the website, for example,targeted advertisements), and the website scanning tool may alsoidentify one or more website cookies within the website that track oneor more interactions of the data subject with the website. The websitescanning tool may use the website category and information related tothe one or more website cookies to produce one or more websiteparameters of the website. In particular embodiments, the system mayapply data subject consent parameters to the data subject's interactionwith the website to determine whether the data subject provided validconsent to the collection, storage, or processing of personal data ofthe data subject. The data subject consent parameters may be determinedbased at least in part on the one or more website parameters associatedwith the particular website and the geo-location of the data subjectwhen the data subject is interacting with the website. In someimplementations, the system may track the data subject's interactionwith the website to determine whether the data subject consentparameters have been satisfied.

In particular embodiments, the determination of the consent parametersrequired and the whether the data subject provided consent may bedynamic. For example, the consent parameters required may be determinedbased on a geo-location of the data subject when accessing the websiteassociated with the entity, a website category of the website associatedwith the entity (e.g., whether the website includes advertisements ornot), and/or data subject information accessed or collected by thewebsite associated with the entity (e.g., via cookies incorporated inthe website associated with the entity).

The system may determine that the data subject is interacting with(e.g., accessing) the website associated with the entity, and consentfor the collection, storing, and/or processing of data subject personaldata is required. The consent parameters may be determined by the systembased on a website category of the website associated with the entityand/or data subject information accessed or collected by the websiteassociated with the entity. In some implementations, for example,website categories may be defined based on whether or not the websiteprovides advertisements, which may be targeted advertisements to thedata subject. Additionally, in some implementations, the website mayinclude one or more cookies that capture personal information of thedata subject and monitor the data subject's activity while accessing thewebsite. The one or more cookies may collect information related to, forexample: (1) mouse speed; (2) mouse hovering; (3) mouse position; (4)keyboard inputs; and/or (5) any other suitable data subject action. Thesystem may determine one or more website categories of the website andinformation associated with the one or more cookies of the website priorto the data subject accessing the website or while the data subject isaccessing the website. Further, in some implementations, thegeo-location of the data subject when the data subject accesses thewebsite may be included in the determination of the degree of consentrequired. For example, each country or region may include privacy lawsrelated to consent, and the country or regional privacy laws may differwith the degree of consent required.

In particular embodiments, the system may determine the data subjectconsent parameters that were determined based at least in part on theone or more website parameters associated with the particular websiteand the geo-location of the data subject when the data subject isinteracting with the website. Additionally, the system may apply thedata subject consent parameters to the data subject's interaction withthe website. In some implementations, the system may track the datasubject's interaction with the website to determine whether the datasubject consent parameters have been satisfied. For example, in onescenario, the data subject consent parameters may require the datasubject to scroll to the bottom of a particular webpage at the websitefor the data subject consent to be provided. However, in anotherscenario, the data subject consent parameters may require the datasubject to select a button on the website indicating that the datasubject consents to the collection of particular personal data (e.g.,explicit consent) for data subject consent to be provided. In particularembodiments, the consent receipt management system may receive the datasubject consent parameters and information related to the data subject'sinteraction with the website for further processing, as describedherein. In some implementations, in response to the system determiningthat the data subject consent parameters have been fulfilled, a consentreceipt may be generated and presented to the data subject, as describedherein.

Cookie Compliance Testing Module and Related Methods

In particular embodiments, any entity (e.g., organization, company,etc.) that collects, stores, processes, etc. personal data may requireconsent from a data subject from whom the personal data is collectedand/or processed. In various embodiments, the entity may be required to,for example, demonstrate that a data subject has freely given specific,informed, and unambiguous indication of the data subject's agreement tothe processing of his or her personal data for one or more specificpurposes (e.g., in the form of a statement or clear affirmative action).In various embodiments, a website scanning tool may be used to determinea website category of the website (e.g., whether personal data is beingused with any presentation provided in the website, for example,targeted advertisements), and the website scanning tool may alsoidentify one or more website cookies within the website that track oneor more interactions of the data subject with the website.

One or more website parameters may be produced based on one or morewebsite categories of the website and information associated with one ormore website cookies that capture data subject information. In variousembodiments, the geo-location of the data subject when the data subjectaccesses the website may be included in the determination of the degreeof consent required. In particular embodiments, the system may applydata subject consent parameters to the data subject's interaction withthe website to determine whether the data subject provided valid consentto the collection, storage, or processing of personal data of the datasubject. The data subject consent parameters may be determined based atleast in part on the one or more website parameters associated with theparticular website and the geo-location of the data subject when thedata subject is interacting with the website. In some implementations,the system may track the data subject's interaction with the website todetermine whether the data subject consent parameters have beensatisfied.

Various aspects of the system's functionality may be executed by certainsystem modules, including a Cookie Compliance Testing Module 9200.Although these modules are presented as a series of steps, it should beunderstood in light of this disclosure that various embodiments of theCookie Compliance Testing Module 9200 described herein may perform thesteps described below in an order other than in which they arepresented. In still other embodiments, the Cookie Compliance TestingModule 9200 may omit certain steps described below. In variousembodiments, the Cookie Compliance Testing Module 9200 may perform stepsin addition to those described (e.g., such as one or more stepsdescribed with respect to one or more other modules, etc.). Variousembodiments of the system are described more fully below.

In particular embodiments, a Cookie Compliance Testing Module 9200 isconfigured for: (1) determining a data subject is interacting with aparticular website; (2) determining one or more website parametersassociated with the particular website, wherein determining the one ormore website parameters associated with the particular website comprises(a) scanning the particular website to determine one or more websitecookies that capture data subject information, and (b) determining awebsite category of the particular website; (3) determining ageo-location of the data subject when the data subject is interactingwith the particular website; (4) determining one or more data subjectconsent parameters based at least in part on the one or more websiteparameters associated with the particular website and the geo-locationof the data subject when the data subject is interacting with theparticular website; and (5) applying the one or more data subjectconsent parameters to the data subject interaction with the particularwebsite.

As may be understood from FIG. 92, when executing the Cookie ComplianceTesting Module 9200, the system begins, at Step 9210, by a data subjectis interacting with a particular website. In particular embodiments, athird-party consent receipt management system may be configured tomanage one or more consent receipts for a particular entity. As may beunderstood in light of this disclosure, a data subject may access aninteraction interface (e.g., via the web) for interacting with aparticular entity (e.g., one or more entity systems). The interactioninterface (e.g., user interface) may include, for example, a suitablewebsite, web form, user interface etc. The interaction interface may beprovided by the entity. Using the interaction interface, a data subjectmay initiate an interaction (e.g., initiate a transaction) with theentity that requires the data subject to provide valid consent (e.g.,because the transaction includes the processing of personal data by theentity). The interaction may include, for example: (1) accessing theentity's website; (2) signing up for a user account with the entity; (3)signing up for a mailing list with the entity; (4) a free trial sign up;(5) product registration; and/or (6) any other suitable interaction thatmay result in collection and/or processing personal data, by the entity,about the data subject.

As may be understood from this disclosure, any particular interactionmay record and/or require one or more valid consents from the datasubject. For example, the system may require a particular data subjectto provide consent for each particular type of personal data that willbe collected as part of the transaction. The system may, in variousembodiments, be configured to prompt the data subject to provide validconsent, for example, by: (1) displaying, via the interaction interface,one or more pieces of information regarding the consent (e.g., whatpersonal data will be collected, how it will be used, etc.); and (2)prompt the data subject to provide the consent.

Continuing to Step 9220, the system is configured for determining one ormore website parameters associated with the particular website, whereindetermining the one or more website parameters associated with theparticular website includes Step 9222, where the system is configuredfor scanning the particular website to determine one or more websitecookies that capture data subject information, and Step 9224, where thesystem is configured for determining a website category of theparticular website. In various embodiments, the system may be used todetermine a website category of the website (e.g., whether personal datais being used with any presentation provided in the website, forexample, targeted advertisements). Steps 9222 and 9224 may be in anyorder relative to one another, or in some embodiments, simultaneously.In various embodiments, scanning the particular website to determine oneor more website cookies that capture data subject information mayinclude: (1) identifying one or more website cookies that capture datasubject information (e.g., (a) mouse speed; (b) mouse hovering; (c)mouse position; (d) keyboard inputs; (e) selection or clickinglocations; (f) scrolling locations within the webpage; and/or (g) anyother suitable data subject action, etc.), and (2) for each of theidentified one or more website cookies that capture data subjectinformation, determining one or more types of personal data captured byeach of the identified one or more website cookies, and storing the oneor more types of personal data captured by each of the identified one ormore website cookies. The type of personal data may be, for example: (1)name; (2) address; (3) telephone number; (4) e-mail address; (5) socialsecurity number; (6) information associated with one or more creditaccounts (e.g., credit card numbers); (7) banking information; (8)location data; (9) internet search history; (10) data subjectinteractions within the particular website; (11) non-credit accountdata; and/or (12) any other suitable personal information discussedherein.

Next, at Step 9230, the system is configured for determining ageo-location of the data subject when the data subject is interactingwith the particular website. The system may be configured to determinethe geo-location based at least in part on an IP address and/or domainof the computing device of the data subject (e.g., in the case of acomputer server or other computing device) or any other identifyingfeature of a particular data subject. Further, the system may, forexample, associate the determined geo-location of the data subject witha plurality of physical locations based at least in part on one or moregeographic boundaries, wherein each may include one or more privacy lawsrelated to the geographic boundaries. These one or more geographicboundaries may include, for example: (1) one or more countries; (2) oneor more continents; (3) one or more jurisdictions (e.g., such as one ormore legal jurisdictions); (4) one or more territories; (5) one or morecounties; (6) one or more cities; (7) one or more treaty members (e.g.,such as members of a trade, defense, or other treaty); and/or (8) anyother suitable geographically distinct physical locations.

At Step 9240, the system is configured for determining one or more datasubject consent parameters based at least in part on the one or morewebsite parameters associated with the particular website and thegeo-location of the data subject when the data subject is interactingwith the particular website. In determining the one or more data subjectconsent parameters, the system may access one or more privacy lawsassociated with the geo-location of the data subject (e.g., based on theone or more geographic boundaries), and apply the accessed privacy lawsto the data subject consent parameters. For example, a privacy lawassociated with the geo-location of the data subject may require thedata subject to be explicitly notified (e.g., presented on the webpage)of the particular type of personal data that is collected by thewebpage.

Continuing to Step 9250, the system is configured to apply the one ormore data subject consent parameters to the data subject interactionwith the particular website. In some implementations, the system maytrack the data subject's interaction with the website to determinewhether the data subject consent parameters have been satisfied. Forexample, in one scenario, the data subject consent parameters mayrequire the data subject to scroll to the bottom of a particular webpageat the website for the data subject consent to be provided. However, inanother scenario, the data subject consent parameters may require thedata subject to select a button on the website indicating that the datasubject consents to the collection of particular personal data (e.g.,explicit consent) for data subject consent to be provided. In particularembodiments, the consent receipt management system may receive the datasubject consent parameters and information related to the data subject'sinteraction with the website for further processing, as describedherein. In some implementations, in response to the system determiningthat the data subject consent parameters have been fulfilled, a consentreceipt may be generated and presented to the data subject, as describedherein.

In various embodiments, the system may, for example, leverage one ormore website scanning techniques to detect whether a website iscorrectly management tracking devices on the site (e.g., based onwhether a JSON object of tags should or should not be triggered) basedat least in part on how controls are toggled on a user interface (e.g.,of user consent preferences as described herein). In some embodiments,the system may be configured to implement one or more event listeners ona webpage to trigger one or more application program interface calls inresponse to detecting a cookie and/or script that should not be set onthe webpage (i.e., because consent has not been established for theparticular script and/or cookie). In still other embodiments, the systemis configured to provide facilitated integrations based at least in parton automated detection of tag management and/or consent managementsystems. In some embodiments, the system is configured to generate acookie notice based at least in part on a type of tracking that thesystem detects on a website via a scan. The system may, for example, beconfigured to dynamically generate a cookie notice based at least inpart on a geo-location of a visitor, enforcement of cookies policies,site scan, and or other suitable factor. The dynamically generatednotice may, for example, be based one or more regulations for aparticular geographic region from which a user is accessing thewebpage/website.

Overview of Consent and Cookie User Interface Validity Testing

In particular embodiments, a consent user interface scoring system maybe configured to evaluate one or more configuration attributes of a userinterface that presents a web form. The system may evaluate the one ormore attributes based at least in part on the configuration of the userinterface of the web form that presents consent information to the datasubject, as described herein. In various embodiments, the one or moreconfiguration attributes may be, for example: (1) selection optionpresented to the data subject for selection to opt in or opt out toconsent to the collection of personal data of the data subject; (2)detailed opt in or opt out selection options (e.g., selecting whether ornot to consent to the collection of each particular type of personaldata, selecting whether or not to consent to each of one or more thirdparties having access to the collected personal data); (3) location andpresentation of a privacy policy (e.g., privacy policy presented on thewebform, privacy policy accessed via a link presented on the web form);(4) one or more selection options for the data subject to be notified ofthe particular personal data collected by the system; (5) data collectedby one or more cookies provided within the web form; (6) etc.

In various embodiments, the system is further configured to access oneor more set of privacy regulations (e.g., CCPA, GDPR, privacy laws,etc.) to compare the one or more configuration attributes to theaccessed privacy regulations or privacy laws. In some embodiments, thesystem may provide results based on the comparison of the one or moreconfiguration attributes to the accessed privacy regulations or privacylaws. For example, the system may determine a user interface consentscore based on the comparison of each of the one or more configurationattributes to the accessed privacy regulations or privacy laws. Invarious embodiments, the user interface consent score may indicate alevel of compliance of the user interface of the web form with theaccessed privacy regulations or privacy laws.

In some implementations, a user interface consent score may bedetermined for each accessed privacy regulations or privacy laws that iscompared to the one or more configuration attributes of the consent userinterface. In some implementations, the user interface consent score maybe a value to identify a level of compliance with one or more of theaccessed privacy regulations or privacy laws (e.g., a numerical value (avalue between 1-100), a tiered value (low, medium, high), acompliant/non-compliant indication, etc.). In some implementations, inresponse to the system determining that the consent user interfaceincludes a particular configuration attribute, the system may indicatethat the consent user interface is not compliant with particular privacyregulations or privacy laws. For example, if a particular privacyregulation requires that a configuration attribute of the consent userinterface include a selection option to opt in or opt out to consent tothe collection of personal data, and the consent user interface does notinclude that particular configuration attribute, then the system mayindicate that the consent user interface is not compliant withparticular privacy regulation.

In various embodiments, as discussed above, the one or moreconfiguration attributes may include data collected by one or morecookies provided within the web form. The one or more cookies maycollect information related to, for example: (1) mouse speed; (2) mousehovering; (3) mouse position; (4) keyboard inputs; (5) an amount of timespent completing the web form; and/or (5) any other suitable datasubject action.

Further, in various embodiments, the system may store the level ofcompliance of the user interface of the web form with the accessedprivacy regulations or privacy laws. In some embodiments, when thesystem indicates that the consent user interface is not compliant withthe particular privacy regulation, the system may automatically modifyone or more configuration attributes of the consent user interface tocause the consent user interface to be compliant with the particularprivacy regulation. In some implementations, when the system indicatesthat the consent user interface is not compliant with the particularprivacy regulation, the system may flag the consent user interface forreview by one or more user (e.g., system administrator or privacyofficer). In response to the user reviewing the flagged consent userinterface, the user may initiate one or more modifications to one ormore configuration attributes of the consent user interface.

Consent User Interface Validity Module and Related Methods

In particular embodiments, any entity (e.g., organization, company,etc.) that collects, stores, processes, etc. personal data may requireconsent from a data subject from whom the personal data is collectedand/or processed. In various embodiments, the entity may be required to,for example, demonstrate that a data subject has freely given specific,informed, and unambiguous indication of the data subject's agreement tothe processing of his or her personal data for one or more specificpurposes (e.g., in the form of a statement or clear affirmative action).The system may generate and manage a consent receipt under one or moretransactions for a data subject. In some implementations, the system mayrecord consent notice information as a part of the consent receipt. Forexample, the generated consent receipt may include information relatedto whether a data subject that is giving consent for purposes ofprocessing personal data associated with the data subject was shown anotice (e.g., a privacy policy) about the processing of the personaldata associated with the data subject.

Various aspects of the system's functionality may be executed by certainsystem modules, including a Consent User Interface Validity Module 9300.Although these modules are presented as a series of steps, it should beunderstood in light of this disclosure that various embodiments of theConsent User Interface Validity Module 9300 described herein may performthe steps described below in an order other than in which they arepresented. In still other embodiments, the Consent User InterfaceValidity Module 9300 may omit certain steps described below. In variousembodiments, the Consent User Interface Validity Module 9300 may performsteps in addition to those described (e.g., such as one or more stepsdescribed with respect to one or more other modules, etc.). Variousembodiments of the system are described more fully below.

In particular embodiments, a Consent User Interface Validity Module 9300is configured for: (1) accessing a consent user interface presented on aweb form, wherein the web form comprises consent information presentedto a data subject completing the web form; (2) determining one or moreconfiguration attributes of the consent user interface; (3) accessingone or more privacy regulations associated with presenting consentinformation; (4) comparing the one or more configuration attributes ofthe consent user interface to each of the one or more privacyregulations; (5) determining a user interface consent score of theconsent user interface with respect to each of the one or more privacyregulations; (6) determining whether the consent user interface iscompliant with each of the one or more privacy regulations; and (7) inresponse to determining that the consent user interface is not compliantwith one or more privacy regulations, flagging the consent userinterface.

As may be understood from FIG. 93, when executing the Personal DataReceipt Module 9300, the system begins, at Step 9310, by accessing aconsent user interface presented on a web form, wherein the web formcomprises consent information presented to a data subject completing theweb form. In particular embodiments, a third-party consent receiptmanagement system may be configured to manage one or more consentreceipts for a particular entity. As may be understood from thedisclosure herein, a data subject may access an interaction interface(e.g., via the web) for interacting with a particular entity (e.g., oneor more entity systems). The interaction interface (e.g., userinterface) may include, for example, a suitable website, web form, userinterface etc. The interaction interface may be provided by the entity.Using the interaction interface, a data subject may initiate atransaction with the entity that requires the data subject to providevalid consent (e.g., because the transaction includes the processing ofpersonal data by the entity). The transaction may include, for example:(1) accessing the entity's website; (2) signing up for a user accountwith the entity; (3) signing up for a mailing list with the entity; (4)a free trial sign up; (5) product registration; and/or (6) any othersuitable transaction that may result in collection and/or processingpersonal data, by the entity, about the data subject. In variousembodiments, the system may access the consent user interface that wouldbe presented to one or more data subjects completing the web form (e.g.,unrelated to an actual transaction or interaction with a data subject).

Continuing to Step 9320, the system is configured for one or moreconfiguration attributes of the consent user interface. In variousembodiments, a consent user interface scoring system may be configuredto evaluate one or more configuration attributes of a user interfacethat presents a web form. The system may evaluate the one or moreattributes based at least in part on the configuration of the userinterface of the web form that presents consent information to the datasubject, as described herein. In various embodiments, the one or moreconfiguration attributes may be, for example: (1) selection optionpresented to the data subject for selection to opt in or opt out toconsent to the collection of personal data of the data subject; (2)detailed opt in or opt out selection options (e.g., selecting whether ornot to consent to the collection of each particular type of personaldata, selecting whether or not to consent to each of one or more thirdparties having access to the collected personal data); (3) location andpresentation of a privacy policy (e.g., privacy policy presented on thewebform, privacy policy accessed via a link presented on the web form);(4) one or more selection options for the data subject to be notified ofthe particular personal data collected by the system; (5) data collectedby one or more cookies provided within the web form; (6) etc.

Next, at Step 9330, the system is configured for accessing, by one ormore processors, one or more privacy regulations associated withpresenting consent information. In various embodiments, the system isconfigured to access one or more set of privacy regulations (e.g., CCPA,GDPR, privacy laws, etc.). The one or more privacy regulations mayinclude regulations related to a privacy policy provided by the entity.The privacy policy may notify the data subject of, for example, (1) whattype of personal data is to be collected, (2) how long the personal datawill be stored, (3) storage features of the personal data (e.g.,encrypted), (4) the purpose of collecting the personal data, (5) rightsof the data subject regarding data collection, (6) etc. The entity or aprivacy regulatory agency may input or provide the applicable one ormore set of privacy regulations to be applied for the consent userinterface.

In various embodiments, the system may be configured to determine theapplicable one or more privacy regulations based on a geo-location ofthe data subject interacting with the consent user interface. The systemmay identify the geo-location based at least in part on an IP addressand/or domain of the computing device of the data subject (e.g., in thecase of a computer server or other computing device) or any otheridentifying feature of a particular data subject. Further, the systemmay, for example, associate the determined geo-location of the datasubject with a plurality of physical locations based at least in part onone or more geographic boundaries, wherein each may include one or moreprivacy laws or one or more privacy regulations related to thegeographic boundaries. These one or more geographic boundaries mayinclude, for example: (1) one or more countries; (2) one or morecontinents; (3) one or more jurisdictions (e.g., such as one or morelegal jurisdictions); (4) one or more territories; (5) one or morecounties; (6) one or more cities; (7) one or more treaty members (e.g.,such as members of a trade, defense, or other treaty); and/or (8) anyother suitable geographically distinct physical locations.

At Step 9340, the system is configured for comparing, by one or moreprocessors, the one or more configuration attributes of the consent userinterface to each of the one or more privacy regulations. The system mayapply each of the one or more privacy regulations to the one or moreconfiguration attributes of the consent user interface. At Step 9350,the system is configured for determining, by one or more processors, auser interface consent score of the consent user interface with respectto each of the one or more privacy regulations. The user interfaceconsent score may be determined (e.g., calculated) in response tocomparing the one or more configuration attributes of the consent userinterface to each of the one or more privacy regulations. For example,the system may determine a user interface consent score based on thecomparison of each of the one or more configuration attributes to theaccessed privacy regulations or privacy laws. In various embodiments,the user interface consent score may indicate a level of compliance ofthe user interface of the web form with the accessed privacy regulationsor privacy laws.

In some implementations, a user interface consent score may bedetermined for each accessed privacy regulations or privacy laws that iscompared to the one or more configuration attributes of the consent userinterface. In some implementations, the user interface consent score maybe a value to identify a level of compliance with one or more of theaccessed privacy regulations or privacy laws (e.g., a numerical value (avalue between 1-100), a tiered value (low, medium, high), acompliant/non-compliant indication, etc.).

In various embodiments, the system may, for each of the one or moreconfiguration attributes, (a) compare each particular configurationattribute to the one or more privacy regulations, and (b) calculate aconfiguration attribute level of compliance for each particularconfiguration attribute based at least in part on comparing theparticular configuration attribute to the one or more privacyregulations. The system may then calculate the user interface consentscore based at least in part on each calculated configuration attributelevel of compliance. Further, in various implementations, the userinterface consent score to a threshold user interface consent scoredetermined based at least in part on each of the one or more privacyregulations. The threshold user interface score may be provided, forexample, by (1) one or more privacy officers of the entity, (2) aregulatory agency that is associated with the one or more privacyregulations, (3) a preset score, (4) etc. The system may compare theuser interface consent score with the threshold user interface consentscore, and in response to determining that the user interface consentscore does not meet (e.g., less than) the threshold user interfaceconsent score, the system may determine that the consent user interfaceis not compliant with the one or more privacy regulations. In someimplementations, the system may determine that the user interfaceconsent score does meet (e.g., greater than or equal to) the thresholduser interface consent score, the system may determine that the consentuser interface is compliant with the one or more privacy regulations.

In some implementations, in response to the system determining that theconsent user interface includes a particular configuration attribute,the system may indicate that the consent user interface is not compliantwith particular privacy regulations or privacy laws (e.g., cause theconsent user interface score to not meet the threshold consent userinterface score). For example, if a particular privacy regulationrequires that a configuration attribute of the consent user interfaceinclude a selection option to opt in or opt out to consent to thecollection of personal data, and the consent user interface does notinclude that particular configuration attribute, then the system mayindicate that the consent user interface is not compliant withparticular privacy regulation.

At Step 9360, the system may be configured for determining whether theconsent user interface is compliant with each of the one or more privacyregulations. The system may, in various embodiments, store the consentuser interface score with the accessed privacy regulations or privacylaws. As described above, the consent user interface score may bedetermined (e.g., calculated) based at least in part on comparing theone or more configuration attributes of the consent user interface toeach of the one or more privacy regulations. In some implementations,the consent user interface score may indicate (e.g., when compared to athreshold consent user interface score) whether the consent userinterface is compliant with each of the one or more privacy regulations.

At Step 9370, in response to determining that the consent user interfaceis not compliant with one or more privacy regulations, the system mayflag the consent user interface. In some embodiments, when the systemindicates that the consent user interface is not compliant with theparticular privacy regulation, the system may automatically modify oneor more configuration attributes of the consent user interface to causethe consent user interface to be compliant with the particular privacyregulation. In some implementations, when the system indicates that theconsent user interface is not compliant with the particular privacyregulation, the system may flag the consent user interface for review byone or more user (e.g., system administrator or privacy officer). Inresponse to the user reviewing the flagged consent user interface, theuser may initiate one or more modifications to one or more configurationattributes of the consent user interface. Further, in someimplementations, the system may determine (e.g., automatically notifiedor automatically updated within the system) that one or more updateshave been made to the one or more privacy regulations. The system, invarious embodiments, may then compare the one or more configurationattributes of the consent user interface to each of the one or moreupdated privacy regulations, calculate an updated consent user interfacescore, and determine whether the consent user interface is compliantwith each of the one or more updated privacy regulations based at leastin part on the consent user interface score.

Automatically Blocking Tracking Tools Overview

It should be understood that, for purposes of this disclosure, “trackingtools” may refer, for example, to cookies, beacons (e.g., visibleelements such as graphics, banners, or buttons; non-pictorial HTMLelements such as the frame, style, script, input link, embed, object,etc. of the web page), scripts, image files, tags, tracking code, and/orany other tracking tools or technology.

In various embodiments, the system may automatically block the use oroperations of one or more tracking tools during the use of a website bya user by analyzing a website to identify one or more of the trackingtools associated with one or more pages of the website and taking one ormore actions to block the use of one or more of the identified trackingtools. For each of one or more webpages associated with the website, thesystem may load the webpage and scan the loaded webpage to identify oneor more of tracking tools loaded and/or referenced by the webpage. Aspart of this identification process, the system may determine source ofa particular identified tracking tools by analyzing the loading of thepage and determining which script function call(s) set the particulartracking tool. In particular embodiments, the system may generate anoutput file with the results of the webpage scanning process. The outputfile may indicate the association of particular tracking tools andparticular source scripts.

Using the results of the webpage analysis (e.g., in the form of theoutput file generated based on the analysis), the system may compare theidentified tracking tools to a database of known tracking technologiesto determine how to categorize each identified tracking tool. Such adatabase may include information regarding vendors, tracking tools,characteristics of known tracking tools, attributes of known trackingtools, the purpose of known tracking tools, scripts associated withknown tracking tools (e.g., that invoke one or more known trackingtools), etc. The system may identify various characteristics and/orattributes of a particular identified tracking tool from the webpage anddetermine one or more known tracking technologies with which theparticular identified tracking tool may (e.g., closely) match in thedatabase of known tracking technologies based on such characteristicsand/or attributes. For example, the system may determine that aparticular identified tracking tool on a webpage is invoked by aparticular source script. The system may then locate that particularsource script in the database of known tracking technologies anddetermine the known tracking tools that are associated with theparticular source script (e.g., as indicated in the database of knowntracking technologies). The system may then determine thecategorization(s) of the particular source script and/or the associatedknown tracking tools (e.g., as indicated in, or based on, the databaseof known tracking technologies) and assign that categorization(s) to theparticular identified tracking tool.

Alternatively, or in addition, the system may determine how tocategorize a particular identified tracking tool based on one or moreflows of data from a browser loading the associated webpage. Inparticular embodiments, a categorization for a particular tracking toolmay include an indication of, or be based at least in part on, one ormore types of personal data that the particular tracking tool mayprocess. A categorization for a tracking tool may also, or instead,include indications for and/or be based at least in part on otherattributes and/or characteristics that may be associated with a trackingtool.

In response to categorizing one or more tracking tools associated with aparticular webpage, the system may generate output (e.g., an outputfile) that includes a data set of the one or more tracking tools and therespective categorization for each tracking tool.

In various embodiments (e.g., after the scanning and categorizationprocess is performed as described above), the system may generate one ormore pieces of computer code (e.g., JavaScript or any other suitablescript) and set the generated code to load as the first script to run onthe page. The system may configure this code to analyze one or moreother scripts (e.g., tracking tools or scripts associated with trackingtools) attempting to load on the webpage (e.g., as the browser rendersthem). The code may be configured to automatically disable scripts that:(1) are not authorized to load (e.g., by default); (2) based on theirrespective category (e.g., as determined by analyzing the output of thescanning process described above); and/or (3) are determined to not becovered by a previous consent granted by the user (e.g., as determinedby accessing a database of user consent information that includes alisting of one or more previous privacy-related consents granted by theuser).

In particular embodiments the system may prompt a user in real time forconsent to load one or more specific categories of scripts that may beotherwise disabled. For example, when the code generated by the systemdetermines that a particular script attempting to load on a webpage isnot covered by previously provided consent, the system may prompt theuser for consent to load a category of script associated with theparticular script. In another example, the system may be configured to,in response to determining that one or more scripts of a specificcategory are loading on a web page, present the user with a consentnotice requesting permission to process data associated with thatspecific category.

In response to receiving such consent from the user, the system may, forexample, be configured to unblock one or more (e.g., all) scripts in thespecific category on the webpage and to allow such scripts to loadand/or process personal data of the specific category based on theuser's consent. In this way, the system may allow tracking tools withinthat specific category to be implemented in conjunction with the one ormore webpages. In response to the user not providing such consent (e.g.,actively or passively indicating that they do not give their consent toexecute scripts in the specific category and/or process personal data ofthe specific category), the system may continue blocking scripts of thespecific category from running on the webpage and/or continue blockingthe processing of personal data of the specific category on the webpage.

Tracking Tool Scanning and Categorization Process

FIG. 94 illustrates an exemplary tracking tool identification andcategorization process that may be performed by a Tracking ToolCategorization Module 9400 according to various embodiments. Inexecuting the Tracking Tool Categorization Module 9400, the systembegins at Step 9410 by loading a webpage and identifying one or moretracking tools and/or tracking-related scripts associated with thewebpage. For example, the system may detect one or more tracking toolsbased on webpage code and/or by detecting the initiation of execution ofone or more tracking tools.

At Step 9420, the system may determine a source for one or more of theidentified tracking tools. The system may identify as a source for aparticular tracking tool one or more scripts or function calls that areexecuted to introduce the particular tracking tool.

In a particular embodiment, to identify a source for a particulartracking tool, the system may analyze one or more flows of data, forexample, between a browser and a server serving the webpage the browseris loading, or between the browser and one or more remote systems (e.g.,remote systems that one or more scripts loading on the webpage attemptto communicate with). For example, the system may scan one or moreresponse headers to identify a source or initiator of the particulartracking tool. For example, using a suitable scanner (e.g., Chromescanner), the system may review one or more response headers that havebeen sent to a browser by a host server associated with a tracking toolin response to the host server receiving an HTTP request. In variousembodiments, the response header may include a date, size, and type offile that the host server is attempting to send to the browser. Theresponse header may also, or instead, include other data, such as dataabout the host server itself. The system may use this header informationto match a source script with a particular tracking tool or otherwisedetermine a source script for a particular tracking tool.

Alternatively, or in addition, at Step 9420, the system may employ aback-end synch with tags to identify a source for a particular trackingtool. In such an embodiment, the system may first determine a hostidentifier from the host field associated with a particular script thatmay be associated with the particular tracking tool. The system may thenmatch the host identifier for the particular script to a host of a knowntracking tool (e.g., as determined from a database of tracking tools) todetermine that the particular source script is associated with the samehost and, therefore, the associated particular tracking tool may beassumed to have a similar tracking purpose.

At Step 9430, the system may generate output, for example an outputfile, that indicates each of the identified tracking tools, theirrespective source scripts, and/or other associated data.

At Step 9440, the system may categorize each of the identified trackingtools, for example, as indicated in the output generate at Step 9430. Tocategorize a tracking tool, according to various embodiments, the systemmay compare data for each identified tracking tool (e.g., tracking tooldata, associated source script data, host data, etc.) with data in adatabase of known tracking tools. Such a database may store informationfor each known tracking tool that may include, but is not limited to:(1) one or more vendors that are associated with the known trackingtool; (2) one or more purposes of the known tracking tool; (3) one ormore types of personal data that the known tracking tool may collectand/or process; (4) one or more host identifiers associated with theknown tracking tool; and/or (5) any other attributes and/orcharacteristics of the known tracking tool. The system may determinewhich one or more of the known tracking tools the identified trackingtool most closely matches based on the comparison. The system may thendetermine a categorization for the identified tracking tool based on thecategorization or other characteristics of the most closely matched oneor more known tracking tools.

For example, if tracking tool data associated with a purpose for aparticular tracking tool matches a purpose of a known tracking tool thatfacilitates the collection of web browsing information, the system mayassociate the category “web browsing information collection” with theparticular tracking tool. In another example, if tracking tool dataassociated with the types of personal data collected by a particulartracking tool matches the types of personal data collected by a knowntracking tool, the system may associate a category associated with thosetypes of personal data collected with the particular tracking tool. Inyet another illustrative example, if tracking tool data indicates that aparticular host server is associated with a particular tracking tool andthe particular host server matches a host server associated with a knowntracking tool, the system may associate the category of the knowntracking tool with the particular tracking tool. In yet anotherillustrative example, if tracking tool data indicates that a particularvendor is associated with a particular tracking tool and that vendormatches a vendor associated with a known tracking tool, the system mayassociate the category of the known tracking tool with the particulartracking tool. Various other particular attributes of tracking tools andrelated data, and any combinations thereof, may be used by the system todetermine a categorization for a particular tracking tool according tovarious embodiments.

At Step 9450, the system may generate and/or populate a data setindicating the identified tracking tools (and/or their respective sourcescripts) and the respective categorization for each. In a particularembodiment, the system may store this data set in an output file of anysuitable format, such as a JavaScript Object Notation (JSON) file thatcan then be embedded into a webpage or code associated with a webpage orwebsite. The system may use this information as described below inautoblocking code to tag particular scripts and to determine whichscripts to allow to execute and which to block.

Automatic Tracking Tool Blocking Process

FIG. 95 illustrates an exemplary automatic tracking tool blockingprocess that may be performed by an Automatic Tracking Tool BlockingModule 9500 according to various embodiments. In executing the AutomaticTracking Tool Blocking Module 9500, the system begins at Step 9510 bygenerating autoblocking code and configuring this code to be the firstscript run on a webpage when it is loaded by a browser (e.g., a webpagepreviously analyzed as described herein). The system may configure theautoblocking code to include the data set output of the process of FIG.94 described above (e.g., embedded with a JSON file containingassociated tracking tool, script, and categorization data). The systemmay configure the autoblocking code to have its own content deliverynetwork (CDN) endpoint. The autoblocking code may be configured on oneor more webpages. The autoblocking code may be in any suitable form,such as JavaScript.

At Step 9520, according to various embodiments, the system (e.g., theautoblocking code) analyzes the scripts attempting to execute as thewebpage is loading using this tracking tool information. The system maytag each such script with a categorization for use in subsequent steps,for example, as indicated in an embedded categorization data set (e.g.,JSON file).

At Step 9530, based on this analysis of Step 9520, the system determineswhether each particular script attempting to load is authorized. Invarious embodiments, the system determines whether the category for eachsuch script is authorized or not. For example, the system may determinethe categorization for each such script based on the data set generatedby the process of FIG. 94 or based on the tag assigned to each suchscript at Step 9520. The system may then determine, based on thecategorization, whether the script should be allowed to execute. Thesystem may be configured to automatically disable any scripts notexplicitly associated with an authorized category and/or any scripts ona listing of known scripts designated to be disabled by default. Thedata set generated by the process of FIG. 94 may include explicitindications of the permissibility of execution of scripts in particularcategories, or that data set may be further used by the system todetermine whether particular scripts are authorized to execute.

In various embodiments, the system may not have enough information todetermine whether a script is authorized to execute. For example, thesystem may detect a script that does not have an associated category. Insuch cases, the system may be configured to automatically disable suchscripts. Alternatively, the system may be configured to automaticallyallow such scripts to run. This setting of whether to run scripts forwhich there is insufficient information may be a user-configurablesetting or preconfigured by a system operator.

In particular embodiments, the system determines whether a script isauthorized or not based on a comparison to scripts in the data set. Forexample, the system may determine that a particular script attempting toexecute on a webpage matches a source script indicated in the data setas not authorized to execute (or does not match a source scriptexplicitly indicated in the data set as authorized to execute). Inresponse, the system may prevent that script from executing. Similarly,the system may determine that a particular script attempting to executeon a webpage matches a source script indicated in the data set asauthorized to execute (or does not match a source script explicitlyindicated in the data set as prohibited from executes). In response, thesystem may allow that script to execute.

In particular embodiments, the system may disable any scripts that auser has not provided consent to execute. For example, if a script is ina category for which the user has declined consent (e.g., the scriptcollects personal data that the user has declined to consent to becollected), the system may automatically disable that script. Todetermine whether the user has consented, the system may access asuitable data structure (e.g., a user consent database) to determinewhether the user has previously granted consent to, for example, processthe user's personal data within one or more specific categories. Thesystem may then use this information to identify any scripts associatedwith the one or more specific categories that the user has providedconsent for. If so, the system may permit the script to run on the webpage. Similarly, the system may use this information to identify anyscripts associated with the one or more specific categories that theuser has declined consent for. The system may prevent such scripts fromrunning on the webpage.

In various embodiments, the system may prompt the user for consent whereit has determined that a script is attempting to run for which the userhas not provided consent. At Step 9540, in response to determining thatthe user has not provided the consent needed to allow a particularscript or be run, the system may prompt the user for such consent. Sucha prompt may be a prompt for consent to run the particular script and/ora prompt for consent to run any script in one or more particularcategories (e.g., one or more particular categories associated with theparticular script).

For example, in various embodiments, the system may be configured to, inresponse to determining that one or more scripts associated withtracking tools of a specific category are loading on a web page, presentthe user with a consent notice requesting permission to process data ofthe specific category. In response to receiving such consent from theuser, the system may, for example, be configured to unblock scripts ofthat specific category (e.g., some or all of such scripts) on thewebpage and allow such scripts to load based on the user's consent. Inresponse to the user not providing such consent (e.g., actively orpassively indicating that the user does not give consent to process dataof the specific category), the system may continue to block scripts ofthe specific category from running on the webpage.

At Step 9550, the system blocks any unauthorized scripts from runningafter determining whether or not such scripts are authorized, and atStep 9560 the system allows authorized scripts, and therefore theirassociated tracking tools, to execute.

In various embodiments, this disclosed tracking tool categorization andautoblocking systems and processes may be applied to any suitable typeof element including, but not limited to, scripts, images (e.g.,beacons), iframe tags, etc. In particular embodiments, an autoblockingscript as described herein may add a relevant Optanon-category-id to aJSON file of tracking tool categorizations depending on a particularcategorization of a source script associated with a particular trackingtool.

CONCLUSION

Although embodiments above are described in reference to various privacycompliance monitoring systems, it should be understood that variousaspects of the system described above may be applicable to otherprivacy-related systems, or to other types of systems, in general.

While this specification contains many specific embodiment details,these should not be construed as limitations on the scope of anyinvention or of what may be claimed, but rather as descriptions offeatures that may be specific to particular embodiments of particularinventions. Certain features that are described in this specification inthe context of separate embodiments may also be implemented incombination in a single embodiment. Conversely, various features thatare described in the context of a single embodiment may also beimplemented in multiple embodiments separately or in any suitablesub-combination. Moreover, although features may be described above asacting in certain combinations and even initially claimed as such, oneor more features from a claimed combination may in some cases be excisedfrom the combination, and the claimed combination may be directed to asub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems maygenerally be integrated together in a single software product orpackaged into multiple software products.

Many modifications and any embodiment described herein of the inventionwill come to mind to one skilled in the art to which this inventionpertains having the benefit of the teachings presented in the foregoingdescriptions and the associated drawings. Therefore, it is to beunderstood that the invention is not to be limited to the specificembodiments disclosed and that modifications and any embodimentdescribed herein are intended to be included within the scope of theappended claims. Although specific terms are employed herein, they areused in a generic and descriptive sense only and not for the purposes oflimitation.

1. A computer-implemented method for automatically blocking the use ofone or more tracking tools during the use of a website by a user, themethod comprising: scanning, by one or more computer processors, one ormore webpages associated with a website to identify one or more trackingtools associated with the one or more webpages; analyzing, by one ormore computer processors, a loading of the one or more webpages toidentify one or more scripts executed during the loading of the one ormore webpages; identifying, by one or more computer processors, based atleast in part on the analysis of the loading of the one or morewebpages, a respective source script associated with each of the one ormore tracking tools, wherein each respective source script invokes arespective tracking tool of the one or more tracking tools; analyzing,by one or more computer processors, each of the one or more trackingtools to determine a categorization of each of the one or more trackingtools based at least in part on comparing data associated with each ofthe one or more tracking tools to know tracking tool data; generating,by one or more computer processors, a computer-readable file comprisingan indicator of each of the one or more tracking tools, an indicator ofthe respective source script associated with each of the one or moretracking tools, and an indicator of the categorization of each of theone or more tracking tools; storing, by one or more computer processorsin a computer memory, the computer-readable file; generating, by one ormore computer processors, a tracking tool blocking script comprising asubset of the computer-readable file; executing, by one or more computerprocessors, the tracking tool blocking script in response to detecting arequest from a user to load the one or more webpages; determining, byone or more computer processors, based at least in part on executing thetracking tool blocking script, whether a particular script of the one ormore scripts is authorized to execute on the one or more webpages; andat least partially in response to determining that the particular scriptof the one or more scripts is not authorized to execute on the one ormore webpages, blocking, by one or more computer processors, based atleast in part on executing the tracking tool blocking script, theparticular script from executing on the one or more webpages.
 2. Thecomputer-implemented method of claim 1, wherein determining whether theparticular script is authorized to execute on the one or more webpagescomprises determining, based at least in part on executing the trackingtool blocking script, that the user has not provided consent for use ofa particular tracking tool of the one or more tracking tools associatedwith the particular script.
 3. The computer-implemented method of claim2, further comprising generating, by one or more computer processors, aprompt requesting consent from the user for use of the particulartracking tool.
 4. The computer-implemented method of claim 2, whereindetermining that the user has not provided consent for the particulartracking tool comprises: determining, by one or more computer processorsexecuting the tracking tool blocking script, based at least in part onthe subset of the computer-readable file, a particular category for theparticular tracking tool; and determining, by one or more computerprocessors executing the tracking tool blocking script, that the userhas not provided consent for tracking tools associated with theparticular category.
 5. The computer-implemented method of claim 4,further comprising generating, by one or more computer processors, aprompt requesting consent from the user for use of the tracking toolsassociated with the particular category.
 6. The computer-implementedmethod of claim 1, wherein the computer-readable file is a JavaScriptObject Notation (JSON) file.
 7. The computer-implemented method of claim6, wherein generating the tracking tool blocking script comprising thesubset of the computer-readable file comprises embedding, by one or morecomputer processors, the JSON file in the tracking tool blocking script.8. An automatic tracking tool blocking system comprising: one or morecomputer processors; and computer memory storing computer-executableinstructions that, when executed by the one or more computer processors,cause the one or more computer processors to perform one or moreoperations comprising: identifying one or more tracking tools associatedwith the one or more webpages; analyzing one or more data flowsgenerated during a loading of the one or more webpages to identify oneor more scripts; identifying, based at least in part on the analysis ofthe one or more data flows, a particular script of the one or morescripts as a particular source script for a particular tracking tool ofthe one or more tracking tools; accessing a database of known trackingtool data; using the database of known tracking tool data to determine acategorization for the particular tracking tool based at least in parton the particular tracking tool and the particular source script;generating one or more pieces of tracking tool analysis computer code;embedding an indicator of the particular tracking tool, an indicator ofthe particular source script, and an indicator of the categorization forthe particular tracking tool in the one or more pieces of tracking toolanalysis code; detecting a subsequent loading of the one or morewebpages; at least partially in response to detecting the subsequentloading of the one or more webpages, executing the one or more pieces oftracking tool analysis computer code; at least partially in response toexecuting the one or more pieces of tracking tool analysis computercode, identifying the particular tracking tool on the one or morewebpages during the subsequent loading of the one or more webpages; atleast partially in response to identifying the particular tracking toolon the one or more webpages during the subsequent loading of the one ormore webpages, tagging the particular tracking tool on the one or morewebpages with the categorization; and determining whether to execute theparticular source script during the subsequent loading of the one ormore webpages based at least in part on the categorization.
 9. Theautomatic tracking tool blocking system of claim 8, wherein analyzingthe one or more data flows comprises analyzing one or more responseheaders received from one or more respective remote systems to identifythe one or more scripts.
 10. The automatic tracking tool blocking systemof claim 9, wherein identifying, based at least in part on the analysisof the one or more data flows, the particular script as the particularsource script for the particular tracking tool is based at least in parton the analysis of the one or more response headers.
 11. The automatictracking tool blocking system of claim 8, wherein determining whether toexecute the particular source script during the subsequent loading ofthe one or more webpages based at least in part on the categorizationcomprises determining whether a user has provided consent for trackingtools associated with the categorization.
 12. The automatic trackingtool blocking system of claim 11, wherein the one or more operationsfurther comprise: at least partially in response to determining that theuser has not provided consent for the tracking tools associated with thecategorization, prompting the user for consent from the user for use ofthe tracking tools associated with the categorization; receiving consentfrom the user for use of the tracking tools associated with thecategorization; and at least partially in response to receiving consentfrom the user for use of the tracking tools associated with thecategorization, allowing the particular source script to execute duringthe subsequent loading of the one or more webpages.
 13. The automatictracking tool blocking system of claim 11, wherein the one or moreoperations further comprise: at least partially in response todetermining that the user has not provided consent for the trackingtools associated with the categorization, prompting the user for consentfrom the user for use of the tracking tools associated with thecategorization; receiving a denial of consent from the user for use ofthe tracking tools associated with the categorization; and at leastpartially in response to receiving the denial of consent from the userfor use of the tracking tools associated with the categorization,preventing the particular source script from executing during thesubsequent loading of the one or more webpages.
 14. The automatictracking tool blocking system of claim 8, wherein the categorization isassociated with one or more types of personal data processed by theparticular tracking tool.
 15. A non-transitory computer-readable mediumstoring computer-executable instructions for automatically blockingtracking tools, the computer-executable instructions comprisinginstructions for: loading, by one or more computer processors, one ormore webpages; during the loading of the one or more webpages:identifying, by one or more computer processors, one or more trackingtools associated with the one or more webpages; analyzing, by one ormore computer processors, the loading of the one or more webpages toidentify one or more scripts executed during the loading of the one ormore webpages; and determining, by one or more computer processors,based at least in part on the analysis of the loading of the one or morewebpages, that a particular script of the one or more scripts is asource script for a particular tracking tool of the one or more trackingtools by determining that the particular script invokes the particulartracking tool during the loading of the one or more webpages; comparing,by one or more computer processors, the source script and the particulartracking tool to known tracking tool data; determining, by one or morecomputer processors, based at least in part on the comparison of thesource script and the particular tracking tool to known tracking tooldata, a corresponding known tracking tool; determining, by one or morecomputer processors; based at least in part on the known tracking tooldata, a categorization for the known tracking tool; assigning, by one ormore computer processors, the categorization for the known tracking toolto the source script; detecting, by one or more computer processors, asubsequent loading of the one or more webpages; and preventing, by oneor more computer processors, based at least in part on thecategorization assigned to the source script, the source script fromexecuting during the subsequent loading of the one or more webpages. 16.The non-transitory computer-readable medium of claim 15, whereinassigning the categorization to the source script comprises: storing, byone or more computer processors in a computer memory, a data structurecomprising an indication of the source script and an indication of thecategorization; and associating, by one or more computer processors inthe computer memory, the source script and the categorization.
 17. Thenon-transitory computer-readable medium of claim 16, wherein storing thedata structure comprises storing the data structure as embedded data inone or more pieces of JavaScript code.
 18. The non-transitorycomputer-readable medium of claim 16, wherein the computer-executableinstructions further comprise instructions for tagging, by one or morecomputer processors, during the subsequent loading of the one or morewebpages, the source script with the indication of the categorization.19. The non-transitory computer-readable medium of claim 15, wherein thecategorization is associated with user consent for use of the particulartracking tool.
 20. The non-transitory computer-readable medium of claim18, wherein the computer-executable instructions further compriseinstructions for prompting a user for consent to use the particulartracking tool.